Change language used in Issues and Milestones

[robnagler]

No description provided.

[robnagler]

I replaced the word Iteration with SOW, because that's what's in the contract. It's also shorter.

Issue language does not refer to the SOW specifically. This allows us to move an Issue from one SOW to another.

I removed prerequisites as they didn't see all that useful at this scale. We have a few issues per SOW, and we can force the order them within the SOW (Milestone), but this seems like too much detail. If we have > 10 issues, maybe it would be useful.

The goal is to keep the Issue language to the "what" with some "how" but very little "why" unless it is unclear. We know we are moving to modern Fortran, and as a part of that, for example, modules will be used.

Other changes and notes:

• We removed cross-platform as a task/goal. We will get the changes on RedHat flavors, and if there's a real need, we can port. We shouldn't add things that will make it harder to move, but we shouldn't spend the time making sure that the software is cross platform.
• We added modules, because this moves in the direction of the goal of the project, whereas all the other activities are supporting operations.
• Try to limit the Issues to single items if they are large, e.g. free form and modules were split out of Replace legacy features #3.
• Issues marked with priorities (1, 2) are for RadiaSoft. Sourcery can assign tasks to us, and are outside the scope of the SOW. This keeps the content of the SOW to within the scope of the contract (work done by Sourcery).
• If Sourcery has issues with any of the contractual issues, please discuss out of band of this repo. (In general, we want to be open, but some things are better discussed in private forums.)