In #86101 we added a warning if bootstrapping was incorrectly configured (and in #92744 we changed it to be emitted every 12h). The logic introduced doesn't take account of `discovery.type: single-node`, so explicitly-single-node clusters will always emit this warning even though they are correctly configured.

Relates https://github.com/elastic/elasticsearch/issues/58393.
server/src/main/java/org/elasticsearch/cluster/coordination/ClusterBootstrapService.java
);
        }
    }
    private void logRemovalWarning(String clusterUUID) {
        logger.warn(
            """
                this node is locked into cluster UUID [{}] but [{}] is set to {}; \
                remove this setting to avoid possible data loss caused by subsequent cluster bootstrap attempts; \
                for further information see {}""",
            clusterUUID,
            INITIAL_MASTER_NODES_SETTING.getKey(),
            bootstrapRequirements,
            ReferenceDocs.INITIAL_MASTER_NODES
        );
    }
    @Override
    public void onFoundPeersUpdated() {
        final Set<DiscoveryNode> nodes = getDiscoveredNodes();
        if (bootstrappingPermitted.get()
            && transportService.getLocalNode().isMasterNode()
            && bootstrapRequirements.isEmpty() == false
            && isBootstrappedSupplier.getAsBoolean() == false) {
            final Tuple<Set<DiscoveryNode>, List<String>> requirementMatchingResult;
            try {
                requirementMatchingResult = checkRequirements(nodes);
            } catch (IllegalStateException e) {
                logger.warn("bootstrapping cancelled", e);
                bootstrappingPermitted.set(false);
                return;
            }