Add order by to bigquery queries (for manifest creation datetimes)

[lcouzens]

Jira Ticket

COST-4975

Description

This change will add an order by to the GCP bigquery we make so when creating manifests for a new provider they are created in sequential order. There is a future code side affect in cluster info because these are created some what randomly in order

Testing

1. Checkout main
2. Restart Koku
3. Add REAL GCP source (Running this QE test is best test_api_ocp_on_gcp_source_cluster_info_infra)
4. If multiple months are ingested this test will likely fail do to the manifest creation order (since latest is previous month when we do lookups for cluster info)
5. Check sources endpoint for status summary (see examples below)
6. Checkout Branch
7. Rerun the above test and it should now pass.
8. check sources endpoint for completed summary state

Example main:
"summary": {
"state": "Pending"
}

Branch Example:
"summary": {
"end": "2024-04-30T10:42:45.011783+00:00",
"start": "2024-04-30T10:42:43.755820+00:00",
"state": "complete"
}

Release Notes

• proposed release note

* [COST-4975](https://issues.redhat.com/browse/COST-4975) Add ordering to bigquery to create manifests in asc order

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.1%. Comparing base (80d964b) to head (5c9adf1).

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #5074     +/-   ##
=======================================
- Coverage   94.1%   94.1%   -0.0%     
=======================================
  Files        377     377             
  Lines      31344   31344             
  Branches    3715    3715             
=======================================
- Hits       29502   29501      -1     
  Misses      1176    1176             
- Partials     666     667      +1     

[lcouzens]

Smoke test failures are failing on main in ephemeral.