Create job to pull Grantee Name and Grant ID data from HSES into Smart Hub database

[pamlo412]

User story 1:
As a TTAS creating an Activity Report, I want to be able to select (rather than type in) the grantees and associated grants my activity addressed so that I can avoid typos or mistakes that would make my report less accurate and searchable.

User story 2 (a specific case of User Story 1):
As a specialist working with a grantee who has been transitioned to Region 13/CDI and given a new grant number, I want to be able to select the name of the grantee with the new CDI grant number so that I'm accurately referencing the grantee and grant.

Acceptance criteria:

• The user can select a grantee name and grant number from a list based on currently active grants
• The Hub recognizes when a grantee's grant has transitioned to CDI, flagging the first grant as inactive (and thus not available for selection in the Activity Report) and the CDI grant as the now active one available for selection in the report.
• The Hub recognizes when a grantee's grant number has changed because a new, continuation grant has been granted, and handles it the same as the CDI grant.
• The user can select multiple grantee name + grant number combinations (1 grantee + multiple grants and also multiple grantees and multiple grants)

Notes:

• Dev plan is to create a job that pulls grantee and grant data from HSES into the Smart Hub database at some regular interval so that it is readily available for us to use in our UI.
• CDI grant numbers are all prefixed with "90CH"
• Glossary entry on CDI grants: https://github.com/HHS/Head-Start-TTADP/wiki/Region-13
• CDI employees will not be TTA Smart Hub users.
• Non-CDI specialists who were working with a grantee before they entered CDI retain access to the grantee's information while the grantee is in Region 13.
• grantees moved to CDI will have new grant numbers so we can mark the previous grant numbers inactive
• it's fine, per Damon, if the user continues to select the old grant number until we have the updated data with the CDI grant number

Exclusions:

• help identifying the correct grant numbers. A grantee may receive multiple grants at the same time; for example, a grant for Head Start programming and a grant for recovery from a disaster. We may try to address this in the future. For the MVP, the specialists need to know which grant numbers to select.
• ability to enter the CDI grant number if it isn't yet in HSES but the specialist knows it. In this case, the specialist will select the pre-CDI grant number

[pamlo412]

Per discussion at grooming today, I've updated this story with the requirements for handling Region 13/CDI grants and closed #96, the story which would have handled those requirements separately.

[rahearn]

• The business and/or user value of a story has been met
• CI pipeline green
• Code is meaningfully tested
• No linting errors or warnings
• UI meets WCAG 2.1 - Levels A and AA
• Code has deployed to a staging environment
• Security scans have passed
• Architectural Decision Records are written for major infrastructure decisions with the Nygard template.
• Boundary and Data Flow Diagrams are updated when a change invalidates the current version.
• Logical Data Model Diagram is updated on DB schema changes.
• Public API methods are documented when added or changed.
• OSCAL templates are completed when security controls are implemented or modified.