feat(Usage Reports): add billing snapshot config service to usage reports

[manukm-ibm]

PR summary

Introducing new CRUD APIs to configure billing reports snapshot.
TRI: https://github.ibm.com/BSS/architecture/blob/master/design-docs/services/billing/apptio-integration.md
Issue: https://github.ibm.com/BSS/metering-deliverables/issues/1990

PR Checklist

Please make sure that your PR fulfills the following requirements:

• The commit message follows the Angular Commit Message Guidelines.
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

Current vs new behavior

Does this PR introduce a breaking change?

• Yes
• No

Other information

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
7 out of 8 committers have signed the CLA.

✅ pyrooka
✅ manukm-ibm
✅ hariarla
✅ padamstx
✅ apoorva9s14
✅ JonahFarc
✅ Rajesh-Pirati
❌ semantic-release-bot
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[padamstx]

There are a few questions/issues to be addressed:

1. Did you really intend to completely overwrite the previous version of the integration tests? There was manually developed code there that probably should be retained. Please see https://github.com/IBM/platform-services-go-sdk/blob/main/update_service.md#updating-integration-testsexamples for instructions on how to update the integration tests and examples code while still retaining the previous manual changes.
2. There were no changes to the examples code, but yet the updates to the generated service code show 5 new operations.
3. It looks like a handful of timestamp-related properties that are supposed to hold "millisecond" values were defined in the API definition as "type number", which results in a language-specific floating point type being used in the generated code. Are you sure that the server behavior supports a floating point value for these properties? I would expect the API definition to use "type integer" and for the fields to be defined with a language-specific integer type.

[padamstx]

@manukm-ibm I took a fresh look at the changes and it looks like 6 operations have been added to the API (based on the changes to the generated service code):

• CreateReportsSnapshotConfig
• GetReportsSnapshotConfig
• UpdateReportsSnapshotConfig
• DeleteReportsSnapshotConfig
• GetReportsSnapshot

We'll need integration tests and working examples for each of those new operations. It might help to generate the int tests and examples off to the side (i.e. into a different output directory), then copy/paste individual sections for each new operation into the checked-in version of the int tests and examples.
Reference: https://github.com/IBM/platform-services-go-sdk/blob/main/update_service.md#updating-integration-testsexamples

[padamstx]

Looks good, but I had just one minor suggested change in the integration tests.

[padamstx]

@manukm-ibm For some reason, it looks like this PR contains 28 commits, but most of those are commits that already were merged into main, so this looks pretty strange :) Could you perhaps rebase your feature branch on the current main branch from the primary repo and clear that up?

[manukm-ibm]

Integration test results of new changes

Examples results of new changes

[padamstx]

LGTM

[ibm-devx-sdk]

🎉 This PR is included in version 0.50.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀