Document/check behaviour of egeria cohort if Kafka becomes unavailable

[planetf1]

#6791 addressed some issues with server startup & Kafka availability
#5471 proposes a framework for checking connector status

This issue is being opened to clarify how Egeria currently behaves if Kafka becomes unavailable during normal operation.

This needs to be documented, we need to check the behaviour is reasonable, and ensure appropriate information is available for any orchestrating environments (k8s, other apps) to act.

Opening to track discussion/investigation

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.