Update the default free message limit when service goes live

[tdlowden]

Looks like when a service is upgraded to live, the daily limit is moved to 250K (the toal MOU tier) but the free message limit stays at 40K. This should be 250K (for pilot). Here is what I see in the platform admin settings for a live service in prod:

[A-Shumway42]

@tdlowden @ccostino
After digging into the code for this issue, I found out why the Free text message allowance doesn't update when a service goes live.

Originally, nothing was being called to update that value so it would stay at 40000 per year. After making a call to the api from billing_api_client in the /switch-live route to update that value, I would still get back 40000 per year.

In the api repo we are calling functions in annual_billing_dao.py from billing/rest.py. These values we are setting/getting are hardcoded based off the year! The code also has some funky logic that is keeping any values at 40,000 for any year 2022 and after. Years 2020 and before have a value of 250,000 For reference, the function is set_default_free_allowance_for_service() in annual_billing_dao.py.

This section of the code needs a re-write.

• The call to get/update the message allowance needs to be added when switching to a live service in the admin repo.
• The logic in set_default_free_allowance_for_service() in the api needs to be updated to not set the default values based off year, but rather off whether the service is live or not?
• The rest of the logic that interacts with this billing portion needs to be assessed to determine whether it's functioning the way we need it to.