Removed requiements, so the work can be started fresh

[john-science]

What is the change?

I have removed all references to requirements in ARMI.

Why is the change being made?

The requirements that were in ARMI were only ever my first pass, from one weekend's worth of work.

Going forward, we are looking at doing a real requirements effort in ARMI, and I feel it is best to just wipe the slate clean. Not to worry, git never forgets.

So, this PR is our starting point for that effort.

---

Checklist

• This PR has only one purpose or idea.
• Tests have been added/updated to verify that the new/changed code works.

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

• The release notes (location doc/release/0.X.rst) are up-to-date with any important changes.
• The documentation is still up-to-date in the doc folder.
• The dependencies are still up-to-date in pyproject.toml.

[john-science]

I am wondering... do we need to add something to the PR checklist that gives people some idea what to do if their PR touches a Requirement, Implementation, or Requirement Test?

Maybe we should also have a section in the docs about that?

[john-science]

@bdlafleur Welcome aboard!

[opotowsky]

🧹

[albeanth]

I am wondering... do we need to add something to the PR checklist that gives people some idea what to do if their PR touches a Requirement, Implementation, or Requirement Test?
Maybe we should also have a section in the docs about that?

Yeah this is a good idea. Let's clean out the old, bring in the new, and then decide what to do on this front. Thoughts?