Versioning support -part 2

[LeiQL]

• Controller: add upsert and delete calls in Reconcile to add required labels for reference maintainance. Not adding labels in webhook as the tags can be a identifier to check whether the labels (rootResource, version and latest tag) are added or not.

• Vendor: change vendor route and add list as default route needs "objectname/version".

• Manager: maintain labels in manager. Add rootResource and version in state and refreshLabels to indicate whether latest label needs to be added or removed. DeleteState accepts ":" object to identify rootResource for latest removal and adding for other objects. Support GetLatestState to fetch latest object

• Provider: k8s state providers handles the calls from manager. Based on refreshLabels bool, maintain tag=latest label.
  - Create new: remove current latest label in the same group (the same rootResource) and add latest label for the new item.
  - Update: check if the current item is the last created. If yes, add latest label.
  - Delete: if current item has latest label, find the last created in the same group and assign latest label.

• API client: accepts /objects/version route in creation and deletion for versioned objects

• Test: fix object reference using new : type

• Temporarily disable instance and target controller unit test. Will fix in other PRs.

• Materialize: require objectState.ObjectMeta.Name as "object:version" to maintain the same naming convension and labels (for example, scenario 04)