Draft: Fetch useful information from Jama

Summary

To clarify

• It's not clear how to identify subset of UCs and Reqs for subsystem verification. Do we need more Jama tags? More UC Jama hierarchy? ReqB are all DPPS (although some of them are specific)? ReqC will have a field? The same as subsystem UCs?
• does this mean all projects will have API credentials to Jama?
• Supposedly DPPS patch releases do not include new UCs/Reqs, so Jama tags can drop that part (optionally?), is this reflected somewhere?
• in jama, "Lower-level requirements (downstream requirements) are defined based on their upstream requirements (vertical trace)", which is why I changed the direction of requirements in Jama!

Goals

• read UCs for release from Jama instead of release plan, optionally
• identify revised vs new based on versions in Jama
• use UC version to identify revised UCs
• parse and present all involved requirements
• build verification graph
• summarize graph in a table
• set default release for the UCs in toolkit version
• harmonize sources of UC/ReleasePlan
  • update UC table to include past UCs and all Jama
  • sync UCs from dpps-use-cases with Jama
  • sync gitlab labels from dpps-use-cases with Jama

How verification of Requirements and UCs is done is described in this note

closes #267