fix ForceReconcile, add unit and e2e tests

[johannes94]

Description

This PR fixes a bug with strategic patch for the endpoint. PATCH /api/rhacs/v1/admin/central/$tenant_id. ForceReconcile in the database would never be set because it is deleted from the map used to merge the original requests values with the patch values.

Also adds an E2E test to make sure force_reconcile can always be set via API because it is required for a lot of SOPs to work properly.

Checklist (Definition of Done)

• Unit and integration tests added
• Added test description under Test manual
• Documentation added if necessary (i.e. changes to dev setup, test execution, ...)
• CI and all relevant tests are passing
• Add the ticket number to the PR title if available, i.e. ROX-12345: ...
• Discussed security and business related topics privately. Will move any security and business related topics that arise to private communication channel.
• Add secret to app-interface Vault or Secrets Manager if necessary
• RDS changes were e2e tested manually
• Check AWS limits are reasonable for changes provisioning new resources

Test manual

only CI/local unit test

# To run tests locally run:
make db/teardown db/setup db/migrate
make ocm/setup OCM_OFFLINE_TOKEN=<ocm-offline-token> OCM_ENV=development
make verify lint binary test test/integration

[ludydoo]

Looks good! 🚀
I find it confusing that the API has both camel and snake case json fields! (e.g. centralDataURL and instance_type).

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johannes94, ludydoo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [johannes94]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[johannes94]

/retest

[johannes94]

Looks good! 🚀 I find it confusing that the API has both camel and snake case json fields! (e.g. centralDataURL and instance_type).

Absolutely, but it is this way to stick to the naming convention of the fleet-manager template that introduced the inconsistency.