Very minor but widespread formatting changes from ruff 0.3.0

[zaneselvans]

Overview

• Apply ruff formatting using the newly released v0.3.0 to all files.
• Doing this as a standalone PR to keep all the tiny one-line autoformatting changes in a single commit that we can ignore for change attribution, but adding the appropriate commit to the .git-blame-ignore-revs file can only happen after this hits main because of our squash-merge-queue.

Testing

• pre-commit checks have passed.
• I skimmed all of the changes and mostly it's the insertion of a blank line after module-level docstrings, plus a handful of reformatted assignment statements, which are a bit more readable.

To-do list

Preview Give feedback

1. Ensure docs build, unit & integration tests, and test coverage pass locally with make pytest-coverage (otherwise the merge queue may reject your PR)
2. For significant ETL changes, ensure the full ETL runs locally
3. For major data coverage & analysis changes, run data validation tests
4. If updating analyses or data processing functions: make sure to update or write data validation tests
5. Update the release notes: reference the PR and related issues.
6. Review the PR yourself and call out any questions or issues you have

[e-belfer]

Yes, definitely makes sense to keep this as a separate PR. Looks good to merge to me.