Ensure we call exclude only on missing processes

[johscheuer]

Description

We've seen some issues with the frequent calling of the fdbcli exclude command to check if a process is excluded from the operator side. We already have logic in the operator code to check if a process is safe to delete (serves no roles) based on the cluster status. The only case where we want to call the exclude command is when the operator has an address that is missing in the cluster status json.

Type of change

Please select one of the options below.

• New feature (non-breaking change which adds functionality)

Discussion

Most of the code changes are unit tests to ensure we cover all important cases.

Testing

Unit tests and the CI pipeline will run the e2e tests.

Documentation

We don't have a dedicated doc for how the operator handles exclusions, I think it would be a good idea to start a doc in a different PR: #1549.

Follow-up

[foundationdb-ci]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: 63f12d2
• Duration 1:48:02
• Result: ✅ SUCCEEDED
• Error: N/A
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)