Streamline use of pre-commit in GitHub workflows

[jakob-keller]

Description of Change

• pre-commit step as part of CI/CD workflow is run across the matrix of Python versions.
• Custom pre-commit GitHub Actions workflow is removed.

Assumptions

• pre-commit.ci is NOT a full replacement: Streamline use of pre-commit in GitHub workflows #1186 (comment)
• Further improvements, such as introducing tox, are out of scope of this PR.

Checklist for All Submissions

• I have added change info to CHANGES.rst
• If this is resolving an issue (needed so future developers can determine if change is still necessary and under what conditions) (can be provided via link to issue with these details):
  • Detailed description of issue
  • Alternative methods considered (if any)
  • How issue is being resolved
  • How issue can be reproduced
• If this is providing a new feature (can be provided via link to issue with these details):
  • Detailed description of new feature
  • Why needed
  • Alternatives methods considered (if any)

Checklist when updating botocore and/or aiohttp versions

• I have read and followed CONTRIBUTING.rst
• I have updated test_patches.py where/if appropriate (also check if no changes necessary)
• I have ensured that the awscli/boto3 versions match the updated botocore version

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.94%. Comparing base (69ceb7a) to head (c4b6995).
Report is 3 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1186   +/-   ##
=======================================
  Coverage   86.94%   86.94%           
=======================================
  Files          64       64           
  Lines        5983     5983           
=======================================
  Hits         5202     5202           
  Misses        781      781           

Flag	Coverage Δ
unittests	86.94% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[webknjaz]

It's usually good to move it into the regular CI/CD workflow. pre-commit.ci has some limitations when it comes to linters needing network access or external environments (which can be the case for pylint).
Though, it's better to exercise the same invocation method as the contributors would (tox/nox/make), to make sure this contributing workflow bit is healthy.

[jakob-keller]

Pre PR we were running pre-commit hooks up to three times on GitHub:

1. as part of the CI/CD workflow, but only for Python 3.11
2. as a dedicated workflow with Python 3.x, currently 3.12
3. through pre-commit.ci (since this week)

This PR would run 1. across the entire matrix (currently Python 3.8 - 3.13) and remove 2.

Further improvements, such as introducing tox, are out of scope of this PR.