style: fix linting and formatting errors

[vanessa-passage]

What's New?

Formatting and linting. In the future, it will only be run on files that are not generated.

Screenshots (if appropriate):

Type of change

• Bug fix (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

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have manually tested my code thoroughly
• I have added/updated inline documentation for public facing interfaces if relevant
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing integration and unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Additional context

[ctran88]

all of the changes under /docs can be dropped since they were supposed to be excluded from the linter/formatter anyways and a new codegen will generate a ton of diffs in the next PR.

this includes the lib/openapi_client file as well

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[vanessa-passage]

@ctran88 This should be ready for final review.