ETCD peer discovery ignores TTL configuration

[mkuratczyk]

A bug introduced during the migration to etcd v3 API: TTL settings are read from the Settings map:

rabbitmq-server/deps/rabbitmq_peer_discovery_etcd/src/rabbitmq_peer_discovery_etcd_v3_client.erl

Lines 74 to 76 in 297d9ed

	node_key_ttl_in_seconds = erlang:max(
	?MINIMUM_NODE_KEY_LEASE_TTL,
	maps:get(etcd_node_ttl, Settings, ?DEFAULT_NODE_KEY_LEASE_TTL)

But that map is constructed ignoring TTL options provided by the user:

rabbitmq-server/deps/rabbitmq_peer_discovery_etcd/src/rabbitmq_peer_discovery_etcd_v3_client.erl

Line 429 in 297d9ed

maps:merge(maps:without([etcd_prefix, etcd_node_ttl, lock_wait_time], Map),

The end result is that the TTL settings cannot be configured and the default values are used.

originally reported on slack:
https://rabbitmq.slack.com/archives/C1EDN83PA/p1678330813982069