Setting a getLastErrorModes write concern value in the replset config breaks the operator

[clrxbl]

Report

When you set config.settings.getLastErrorModes in the replicaset config to something containing a write concern, the operator does not handle this properly and marks the cluster as unhealthy.

More about the problem

Error: failed to update config members: get replset config: failed to decode to replSetGetConfig: error decoding key config.settings.getLastErrorModes.EnsureGlobal.region: cannot decode 32-bit integer into a string type

Steps to reproduce

conf = rs.conf()
conf.settings.getLastErrorModes = { EnsureGlobal: { "region": 1 }}
rs.reconfig(conf)

A custom write concern requires an integer to be set, but the operator tries to parse it as string. It is not possible as a workaround to set it as string, as MongoDB refuses to apply this change

MongoServerError[InvalidReplicaSetConfig]: Expected getLastErrorModes.EnsureGlobal.region to be a number, not string

Versions

Kubernetes 1.31.1+k3s1
Operator 1.18.0
MongoDB 7.0.15-9

Anything else?

No response