[8.x](backport #4344) github-actions(pre-commit): detect merge conflicts and shebangs

[mergify]

What does this PR do?

Use pre-commit with a subset of checks and run in the CI always.

Why is it important?

Similarly done at elastic/beats#42377

Help with detecting merge conflicts or shebang issues

How to test this PR locally

Design Checklist

• I have ensured my design is stateless and will work when multiple fleet-server instances are behind a load balancer.
• I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.
• I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.

Checklist

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool

Related issues

---

This is an automatic backport of pull request #4344 done by [Mergify](https://mergify.com).

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[mergify]

This pull request has not been merged yet. Could you please review and merge it @v1v? 🙏

[mergify]

This pull request has not been merged yet. Could you please review and merge it @v1v? 🙏