Updating Versioning per-compliance requirements

[kylanerace]

Proposed changes

• filelock from 3.20.0 to 3.20.1
• identify from 2.6.12 to 2.6.15
• iniconfig from 2.1.0 to 2.3.0
• pre-commit from 4.3.0 to 4.5.0
• build from 1.2.2.post1 to 1.3.0
• click from 8.2.1 to 8.3.1

Covers:

• Bump click from 8.2.1 to 8.3.1 #157
• Bump build from 1.2.2.post1 to 1.3.0 #162
• Bump pre-commit from 4.3.0 to 4.5.0 #163
• Bump iniconfig from 2.1.0 to 2.3.0 #164
• Bump identify from 2.6.12 to 2.6.15 #165
• Bump filelock from 3.20.0 to 3.20.1 in the pip group across 1 directory #166

Types of changes

What types of changes does your code introduce to the Encrypted Computing SDK project?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you are unsure about any of them, do not hesitate to ask. We are
here to help! This is simply a reminder of what we are going to look for before
merging your code.

• I have read the CONTRIBUTING agreement
• Current formatting and unit tests / base functionality passes locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Further comments

Merging individual auto PR into single PR