[DEV-14487] Additional changes for transition of initial_report_date and last_modified_date to timestamp

[sethstoudenmier]

Description:

Updates additional usages of last_modified_date to be consistent with the change to a datetime. And updates management commands to allow copy back of a table to support swap in place.

Technical Details:

Migrations were updated / created to support the swap in place. The temporary column names for the swap in place are designed to match temporary columns that will be added to the corresponding Delta tables.

A few other fields were updated to be consistent with the data they are pulled from.

Field updates:

• initial_report_date on transaction_fpds was updated to support datetime
• initial_report on transaction_fpds was updated to support datetime
• last_modified_date on award_search was updated to support datetime
• last_modified_date on subaward_seach in was updated to support datetime
• last_modified_date on transaction_normalized was updated to support datetime

Not style check related udpates:

• Indexes and constrains are now sorted when running the copy_table_metadata command; promotes a consistent performance across runs
• A new --additional-columns flag is added to load_table_from_delta to support copying from Delta to Postgres the target table along with columns that aren't part of the table definition in code; useful for swap in place

Requirements for PR Merge:

1. N/A Unit & integration tests updated
2. API documentation updated (examples listed below)
   1. API Contracts
   2. API UI
   3. Comments
3. Data validation completed (examples listed below)
   1. Does this work well with the current frontend? Or is the frontend aware of a needed change?
   2. Is performance impacted in the changes (e.g., API, pipeline, downloads, etc.)?
   3. Is the expected data returned with the expected format?
4. Appropriate Operations ticket(s) created
5. Jira Ticket(s)
   1. DEV-14487

Explain N/A in above checklist: