Edit Annual Limit client to add new data around year info

[jzbahrai]

Summary | Résumé

Added year to date information in the annual limit client

        notifications_v2: {
            sms_delivered_today: int,
            email_delivered_today: int,
            sms_failed_today: int,
            email_failed_today: int,
            total_sms_fiscal_year_to_yesterday: int,
            total_email_fiscal_year_to_yesterday: int,
        }

Code is written to be backwards compatible

Related Issues | Cartes liées

https://app.zenhub.com/workspaces/notify-planning-614b3ad91bc2030015ed22f5/issues/gh/cds-snc/notification-planning/1767

Test instructions | Instructions pour tester la modification

TODO: Fill in test instructions for the reviewer.

Release Instructions | Instructions pour le déploiement

None.

Reviewer checklist | Liste de vérification du réviseur

• This PR does not break existing functionality.
• This PR does not violate GCNotify's privacy policies.
• This PR does not raise new security concerns. Refer to our GC Notify Risk Register document on our Google drive.
• This PR does not significantly alter performance.
• Additional required documentation resulting of these changes is covered (such as the README, setup instructions, a related ADR or the technical documentation).

⚠ If boxes cannot be checked off before merging the PR, they should be moved to the "Release Instructions" section with appropriate steps required to verify before release. For example, changes to celery code may require tests on staging to verify that performance has not been affected.

[whabanks]

LGTM! Just want to clarify what our migration plan is. Are we running a script to migrate existing key values over to the v2 structure? Or are we just waiting for that to occur naturally over time?

[jzbahrai]

@whabanks the transition plan will be to just naturally wait for the new api/admin code to replace the old keys/ no script should be necessary