AB2D-5782 Database changes for AttributionDataShare Lambda

[smirnovaae]

🎫 Ticket

https://jira.cms.gov/browse/AB2D-5782

🛠 Changes

• Added create_current_mbi_table.sql liquibase file where I create a new table public.current_mbi and insert unique current mbis from public.coverage table.
• Added create_current_mbi_procedure.sql liquibase file where I create a procedure to insert values from 2023 partition to public.current_mbi table

ℹ️ Context for reviewers

Performance of the AttributionDataShare Lambda in production will need some kind of persistence. An easy way to do this based on our existing architecture that the engineering team has discussed is by utilizing a database procedure.

✅ Acceptance Validation

Deployed the branch on dev:

🔒 Security Implications

• This PR adds a new software dependency or dependencies.
• This PR modifies or invalidates one or more of our security controls.
• This PR stores or transmits data that was not stored or transmitted before.
• This PR requires additional review of its security implications for other reasons.

If any security implications apply, add Jason Ashbaugh (GitHub username: StewGoin) as a reviewer and do not merge this PR without his approval.

[Sadibhatla]

please keep a 2024 included stored proc ready too.. as by the time we actually deploy it , it need to be pulling from 2024 tables .. (so have the script , comment and include in the PR ).. Evrything looks great ..