fix: Sort directories and files to ensure they are always processed in the same order

[pdecat]

Description

Sort directories and files to ensure they are always processed in the same order during hashing and zip file creation.

Motivation and Context

The order files are walked is not determined by default which can result in different archives created from different workspaces:

# diff -y -W 160 <(unzip -vl
.terraform/lambda-start-scheduled-execution-builds/81c20fecbe4e25f6e7dce7b8ee1a151ea6c76e84eeb25cc937f8ddbeeff54777.zip) <(unzip -vl .terraform/lambda-start-scheduled-exe
cution-builds/f6c01d9d2d57cd416967d66704cc421eb24f72aab55da0fd18f7e676ab8a5491.zip)
Archive:  .terraform/lambda-start-scheduled-execution-builds/81c20fecbe4e25f6 | Archive:  .terraform/lambda-start-scheduled-execution-builds/f6c01d9d2d57cd41
 Length   Method    Size  Cmpr    Date    Time   CRC-32   Name                   Length   Method    Size  Cmpr    Date    Time   CRC-32   Name
--------  ------  ------- ---- ---------- ----- --------  ----                  --------  ------  ------- ---- ---------- ----- --------  ----
       0  Defl:N        2   0% 2021-07-05 15:51 00000000  __init__.py         |      901  Defl:N      473  48% 2021-07-12 12:11 cc20a2a7  main.py
     901  Defl:N      473  48% 2021-07-05 17:21 cc20a2a7  main.py             |        0  Defl:N        2   0% 2021-07-12 12:11 00000000  __init__.py
--------          -------  ---                            -------               --------          -------  ---                            -------
     901              475  47%                            2 files                    901              475  47%                            2 files

Breaking Changes

N/A

How Has This Been Tested?

• I have tested and validated these changes using one or more of the provided examples/* projects

Tested with examples/build-package.

[antonbabenko]

This is a good idea to be consistent with ordering. Merging this one.

[antonbabenko]

v2.13.0 has been just released.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.