Ticket9007 config macro fix

[Chsudeepta]

Description of work

Fixes the bug reported here

[Tom-Willemsen]

Why do we need this set - we're not doing anything with it?

[Chsudeepta]

Agreed. Removed.

[Tom-Willemsen]

Minor regression: when setting a macro for the first time, the value textbox now needs a double click to begin entering text, rather than a single click before you could start typing previously.

[Tom-Willemsen]

As @FreddieAkeroyd reported on teams, if you untick the use default box but don't actually type a value, it uses value = null and doesn't write it to the XML in the blockserver. It should use value = "" rather than null initially for this case.

This causes the config to be corrupt and the blockserver to fail to load it on restart:

[2026-08-11 14:46:31.935967] MAJOR: Could not load last configuration. Message was: Element '{http://epics.isis.rl.ac.uk/schema/iocs/1.0}macro': The attribute 'value' is required but missing., line 36

[Tom-Willemsen]

Test name is now wrong.

[Chsudeepta]

Corrected. Name hasn't been changed.

[Tom-Willemsen]

With the latest change, I started with a brand-new TRITON_02 IOC and added 4 macros like this:

When I then save this new IOC, the macros are saved in the XML as:

	<ioc name="TRITON_02" autostart="true" restart="true" simlevel="none">
		<macros>
			<macro name="CHANNEL_POLL_RATE" value="" description="The poll rate of channel values." pattern="^.*$" defaultValue="10 second" hasDefault="YES"/>
			<macro name="IPADDR" value="" description="IP address to connect to." pattern="^.*$" defaultValue="localhost" hasDefault="YES"/>
			<macro name="IPPORT" value="" description="Port to connect to (defaults to 33576)." pattern="^[0-9]+$" defaultValue="33576" hasDefault="YES"/>
			<macro name="POLL_RATE" value="" description="The poll rate of non-channel values." pattern="^.*$" defaultValue="1 second" hasDefault="YES"/>
		</macros>
		<pvs/>
		<pvsets/>
	</ioc>

i.e. all the values are value="". If I then go to save the config again, then they will be saved correctly the second time.

[Tom-Willemsen]

It looks like we are somehow mixing the XML that defines macro-defaults (the one with a description attribute), with the JSON which gets passed to the blockserver and later turned into XML. This feels like the most likely source of many of these bugs. These two XMLs should be entirely independent.