fix(openstack-sync-operator): clear orphaned profiles when prune is off and few improvements

[haseebsyed12]

What does this change do?

Upgrade impact

• This change requires operator action to upgrade. If checked, add the
  upgrade-impact label and a release note: run scriv create from the
  repository root and describe the required action in the generated
  changelog.d/ file. See RELEASING.md.

Operator action means anything a deployment has to do beyond a normal resync:
deploy repo or values changes, new or removed secrets, enabling or disabling a
component, or a manual one-time step.

[cardoe]

There is still a lifecycle gap when PRUNE is false.

The orphan sweep is called from RouterFlavorPlugin.prune(), but the framework does not obtain a connection for a deletion-only run when plugin.config.prune is false. If a reconcile creates a service profile and then fails before binding it, deleting the final CR gives us one last binding context containing the credentials. However, there are no resources to reconcile, so no connection is cached, and _run_prune skips the group before RouterFlavorPlugin.prune() can call prune_orphaned_profiles(). With no CRs left, later scheduled runs also have no credentials and the orphan remains indefinitely.

I think the framework or plugin contract needs to distinguish flavor pruning from safe orphan collection so this plugin can request a connection even when PRUNE is false. Please add an integration test through run_sync() with a deletion-only input, PRUNE=false, and an orphaned managed profile; calling RouterFlavorPlugin.prune() directly does not exercise the connection gate that causes the problem.