revise: preamble and version stmt lint rules

[a-frantz]

Describe the problem or feature in addition to a link to the issues.

This revises the preamble+version formatting rules to use some more whitespace. PreambleComments and PreambleWhitespace have been refactored into 3 rules: PreambleFormatting, VersionFormatting, and PreambleCommentAfterVersion.

The tests have been cleaned up. This means using lint directives judiciously and generally following more of our own lints within the tests.

Some rules that were emitting warnings have been downgraded to notes.

Many TODOs have been logged. We generally prefer logging issues to TODO comments, but I didn't want to flood the issues with a bunch of tiny complaints. Maybe that's preferred?

Before submitting this PR, please make sure:

• You have added a few sentences describing the PR here.
• You have added yourself or the appropriate individual as the assignee.
• You have added at least one relevant code reviewer to the PR.
• Your code builds clean without any errors or warnings.
• You have added tests (when appropriate).
• You have updated the README or other documentation to account for these
  changes (when appropriate).
• You have added an entry to the relevant CHANGELOG.md (see
  "keep a changelog" for more information).
• Your commit messages follow the conventional commit style.

[peterhuene]

Many TODOs have been logged. We generally prefer logging issues to TODO comments, but I didn't want to flood the issues with a bunch of tiny complaints. Maybe that's preferred?

I think it's find to create either a single issue to track the various TODOs as an item in a check list or to track each independently if it makes sense to do.

[peterhuene]

Looks good! Just a few feedback comments.

I also tried to comment on the TODOs where encountered to act as a reminder to create tracking issues / a singular tracking issue; I might have missed some.

[a-frantz]

Many TODOs have been logged. We generally prefer logging issues to TODO comments, but I didn't want to flood the issues with a bunch of tiny complaints. Maybe that's preferred?

I think it's find to create either a single issue to track the various TODOs as an item in a check list or to track each independently if it makes sense to do.

opened #203 with 6 items to track

[peterhuene]

Looks good!