Use black formatting

[bhazelton]

Description

More consistent code formatting.

For review purposes: I only made changes by hand in .pre-commit-config.yaml and pyproject.toml to set up black. Then I ran pre-commit run --all and let black make changes. I then had to shorten a couple of lines that had strings that black couldn't break up. I also turned formatting off for a small section in simsetup.py where the hera text catalog is defined to allow the arrays of numbers to keep their existing formatting. All other changes were made automatically by black.

Motivation and Context

closes #272

Types of changes

• [ ] 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 change)
• [ ] Reference simulation update or replacement
• [ ] Documentation change (documentation changes only)
• [ ] Version change
• [x] Build or continuous integration change

Checklist:

For all pull requests:

• [x] I have read the contribution guide.
• [x] My code follows the code style of this project.

Build or continuous integration change checklist:

• [ ] If required or optional dependencies have changed (including version numbers), I have updated the readme to reflect this.
• [ ] If this is a new CI setup, I have added the associated badge to the readme and to references/make_index.py (if appropriate).

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.86%. Comparing base (9ad0c74) to head (6e5bdf8).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #454 +/- ## ======================================= Coverage 99.86% 99.86% ======================================= Files 12 12 Lines 2161 2161 ======================================= Hits 2158 2158 Misses 3 3 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.