Feature/issue 229 - Create new database tables for version D collections

[torimcd]

Github Issue: closes #229 - Create new database tables for version D collections

Description

New SWOT hydrology data collections are coming in January 2025. We need new database tables to support the new data version.

Overview of work done

• update dynamodb terraform to add version d tables
• rework how collection name/table info is handled in constants throughout all hydrocron modules
• update unit tests

Overview of verification done

Unit tests pass

Overview of integration done

No integration tests yet as we don't have any version D data to test with yet.

PR checklist:

• Linted
• Updated unit tests
• Updated changelog
• Integration testing

See Pull Request Review Checklist for pointers on reviewing this pull request

[nikki-t]

This looks great! I had one comment on table names but I don't think that we necessarily have to do anything at this point.

I think we had decided to hold off on merging until we had some version D data to work with in SIT. But we could merge this into develop and then perform the SIT testing on the combined database and API updates too.

[nikki-t]

Just trying to think out the impact of the table names. I don't think we want to change the existing ones as that would be really impactful - although I bet we could retire them after the switch to version D data. Do we want to differentiate between the two tables in a more generic way, not sure the best way to do this? Or should we plan to add a new table for each new version and delete the previous version that is no longer in use?