Hive SyncSet GenevaActions

[SrinivasAtmakuri]

Implements:

1. Geneva Action to list selectorsyncsets for a given hive instance
2. Geneva Action to retrieve an individual selectorsyncset on a given hive instance
3. Geneva Action to list syncsets for a cluster defined by resource id in a hive instance
4. Geneva Action to retrieve an individual syncsets on a given hive instance

How to call:

List selector/syncsets - /admin/hivesyncset?namespace={namespace}?isSyncset
Get a selector/syncset - /admin/hivesyncset/syncsetname/{syncsetname}?namespace={namespace}?isSyncSet

Notes:

1. namespace should be "" for selectorsyncsets
2. namespace cannot be "" for syncsets
3. isSyncSet can be true/false, setting it changes from using default selectorsyncset to syncset

Which issue this PR addresses:

Fixes

What this PR does / why we need it:

Test plan for issue:

Testing is underway., below is the plan.,

1. Connect to shared AKS cluster's hive
2. Create a cluster and Syncset in CD namespace and SelectorSyncSet with hive
3. Run admin GA using curl via localrp

Is there any documentation that needs to be updated for this PR?

How do you know this will function as expected in production?

[mociarain]

Would it make more sense to add this using the builder pattern or something similar:https://medium.com/@reetas/clean-ways-of-adding-new-optional-fields-to-a-golang-struct-99ae2fe9719d?

What do you think?

[SrinivasAtmakuri]

the rational for creating a new interface is bcoz the syncsets are not cluster scoped and hive instance scoped, so its cleaner to have a new interface which implements syncset functions.

[pepedocs]

I have added my comments mostly for enhancement. However I'd like to request changes for the usage of HTTP 403 Forbidden status as I've specified. HTTP 400 Bad Request should be the right response for client requests that lack parameters or wrong parameters.

[bitoku]

It would be better to refactor like https://github.com/Azure/ARO-RP/pull/3665/files first to focus on the actual change.

[bitoku]

We want e2e tests for this feature.

[SrinivasAtmakuri]

I have added my comments mostly for enhancement. However I'd like to request changes for the usage of HTTP 403 Forbidden status as I've specified. HTTP 400 Bad Request should be the right response for client requests that lack parameters or wrong parameters.

Resolved, made the changes.

[github-actions]

Please rebase pull request.

[SudoBrendan]

flagging this as needing a rebase on master to pick up the .bingo changes.

[github-actions]

Please rebase pull request.

[SrinivasAtmakuri]

/azp run ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).