Expose some skip inspection options for `armi.init` and `db.loadOperator`

[opotowsky]

What is the change?

This exposes a skipInspection option to armi.init and a handleInvalids option db.loadOperator. The original behavior is retained by default.

Why is the change being made?

Folks write scripts that use the API, and when they run these scripts, they are often stuck in settings inspection mode (typing y + <enter> over and over if they are loading older settings files). This helps them skip said inspections so they can run scripts without babysitting them.

---

Checklist

• [x] This PR has only one purpose or idea.
• [ ] Tests have been added/updated to verify any new/changed code. (WIP: this was harder than I thought it would be!)

• [x] The code style follows good practices.
• [x] The commit message(s) follow good practices.

• [x] The release notes have been updated if necessary.
• [x] The documentation is still up-to-date in the doc folder.
• [x] The dependencies are still up-to-date in pyproject.toml.

[john-science]

Looks great. It really could use some unit testing for the DB stuff. (Testing armi.init() can be skipped.)

[jakehader]

Is this only needed for interactive mode? What's the scenario where someone needs to babysit settings queries? Not a huge fan of adding more kwargs to init so I'm curious if we have the right check inputs design.

[opotowsky]

Is this only needed for interactive mode? What's the scenario where someone needs to babysit settings queries? Not a huge fan of adding more kwargs to init so I'm curious if we have the right check inputs design.

Yes this is needed for interactive mode, when someone runs a python script on the command line.

I guess we could skip the checkInputs on armi init....but I didn't feel empowered to make such a big change.