Document and test clang format options; append style.md details

[tanaya-mankad]

Description

Replace the content in this section with:

• The motivation and context for this change (if it is not immediately clear from the title)
• If it fixes an open issue, specify the issue number (e.g., "fixes #XXXX")
• A summary of the behavior expected from this change
• A description of tests performed

Author Progress Checklist:

• Open draft pull request
  • Make title clearly understandable in a standalone change log context
  • Assign yourself the issue
  • Add at least one label
• Make code changes (if you haven't already)
• Self-review of code
  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have added comments to my code, particularly in hard-to-understand areas
  • I have only committed the necessary changes for this fix or feature
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have ensured that my fix is effective or that my feature works as intended by:
    • exercising the code changes in the test framework, and/or
    • manually verifying the changes (as explained in the the pull request description above)
  • My changes pass all local tests
  • My changes successfully passes CI checks
• Move pull request out of draft mode and assign reviewers
• Iterate with reviewers until all changes are approved
  • Make changes in response to reviewer comments
  • Re-request review in GitHub

Reviewer Checklist:

• Read the pull request description
• Perform a code review on GitHub
• Confirm all CI checks pass and there are no build warnings
• Pull, build, and run automated tests locally
• Perform manual tests of the fix or feature locally
• Add any review comments, if applicable
• Submit review in GitHub as either
  • Request changes, or
  • Approve
• Iterate with author until all changes are approved
• If you are the last reviewer to approve, merge the pull request and delete the branch

[nealkruis]

Minor questions, but this is probably good enough to have a discussion.

[nealkruis]

This violates the file naming rule above.

[nealkruis]

This should maybe be across all names (not just variable names?)

[michael-okeefe]

Looks good to me. Thank you.