Enable option to set `skupper.io/default-site-sizing="no"` for skupper site sizing configmap

[vsomwanshi]

Describe the bug Scenario : When we are planning to create different skupper site sizing configmap profile to deploy a skupper site under the namepsace where the skupper controller is hosted so it can read that configmap profil;e based on the labels value set and deploy the site.

In such cases we need to set skupper.io/default-site-sizing: "yes" only in one configmap and exclude from other configmaps so even if someone missed to set Site.spec.settings.size in site configuration then controller should deploy a site using the configmap which has parameter default-site-sizing: "yes".

For testing i set skupper.io/default-site-sizing: "no" in one of the configmap profile still cIncluded the skupper.io/default-site-sizing: no annotation, probably while debugging, and controller mistook that for "yes" and started behaving weird where controller was reading the configmap which had skupper.io/default-site-sizing: "no" as well as skupper.io/default-site-sizing: "yes". The controller was probably in a nondeterministic state where those profiles were fighting for precidence.

How To Reproduce

Create 2 or more configmap profiles. Set skupper.io/default-site-sizing: "no" to one of the profile and set skupper.io/default-site-sizing: "yes" to another configmap profle.

Expected behavior N.A

Environment details

• Skupper CLI: 2.1.0
• Skupper Operator (if applicable): [e.g. 1.5.0, 1.4.3]
• Platform: OpenShift

Additional context Add any other context about the problem here.