Bump to ops 2.10 and remove workaround for excluding breaking apps from relation-broken events

[ca-scribner]

Context

The resource dispatcher's kubernetes_manifest lib has the following workaround:

resource-dispatcher/lib/charms/resource_dispatcher/v0/kubernetes_manifests.py

Lines 327 to 354 in 6802b73

	def get_name_of_breaking_app(relation_name: str) -> Optional[str]:
	"""
	Get the name of a remote application that is leaving the relation during a relation broken event by
	checking Juju environment variables.
	If the application name is available, returns the name as a string;
	otherwise None.
	"""
	# In the case of a relation-broken event, Juju non-deterministically may or may not include
	# the breaking remote app's data in the relation data bag. If this data is still in the data
	# bag, the `JUJU_REMOTE_APP` name will always be set. For these cases, we return the
	# remote app name so the caller can remove that app from the data bag before using it.
	#
	# To catch these cases, we inspect the following environment variables managed by Juju:
	# JUJU_REMOTE_APP: the name of the app we are interacting with on this relation event
	# JUJU_RELATION: the name of the relation we are interacting with on this relation event
	# JUJU_HOOK_NAME: the name of the relation event, such as RELATION_NAME-relation-broken
	# See https://juju.is/docs/sdk/charm-environment-variables for more detail on these variables.
	if not os.environ.get("JUJU_REMOTE_APP", None):
	# No remote app is defined
	return None
	if not os.environ.get("JUJU_RELATION", None) == relation_name:
	# Not this relation
	return None
	if not os.environ.get("JUJU_HOOK_NAME", None) == f"{relation_name}-relation-broken":
	# Not the relation-broken event
	return None
	return os.environ.get("JUJU_REMOTE_APP", None)

This should not be needed as of ops 2.10.0 release. We should test whether 2.10.0 successfully fixes this issue, and if so remove the current workaround.

What needs to get done

1. test whether ops 2.10.0 fixes the relation-broken handling issue
2. remove the workaround
3. update any charms that use this library to remove the workaround from all charms

Definition of Done

1. publish an updated charm library with the hack removed
2. update all charms that use the library (or create separate issues for them to be updated)

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5292.

This message was autogenerated