setting a cluster property during a partial upgrade might prevent the node from starting

[andijcr]

Version & Environment

Redpanda version: v23.2

requires snapshots

scenario: rollback from a partial upgrade, a new cluster property A

t1:
node1. vX
node2. vX
node3. v(X+1)
t2:
set prop A=val to node3, prop get's accepted. node1 and node2 record it and do nothing with it
t3:
rollback node 3 to vX
node 3 refuse to start with main - application.cc:388 - Failure during startup: std::out_of_range (Property A not found)

what should happen

node 3 with vX should ignore A

in general it's a bad idea to set a cluster property while upgrading a node, but it's not something outright disallowed and it should be handled