Allow an on_update as well as a _RecordUpdater

[evalott100]

In

PandABlocks-ioc/src/pandablocks_ioc/ioc.py

Lines 663 to 682 in 8e25d64

	record_updater = None
	if (
	"on_update" not in kwargs
	and "on_update_name" not in kwargs
	and record_creation_func in OUT_RECORD_FUNCTIONS
	):
	record_updater = _RecordUpdater(
	record_info,
	self._record_prefix,
	self._client,
	self._all_values_dict,
	labels if labels else None,
	)
	extra_kwargs["on_update"] = record_updater.update
	extra_kwargs["DESC"] = trim_description(description, record_name)
	record = record_creation_func(
	record_name, *labels, *args, **extra_kwargs, **kwargs
	)

A record updater is created to send data back to the panda.

• Nowhere in the code passes on_update_name so this should be removed.
• We should allow for the passing of a seperate argument record_updater, which can be merged with the passed in on_update.
• We should allow for records with their own on_update which aren't _RecordUpdater.updates to also be given a _RecordUpdater.

[AlexanderWells-diamond]

Nowhere in the code passes on_update_name so this should be removed.

I added that as defensive code in case we ever do use it. If someone were to use it they would likely have an unexpected result, as the code would break in an unrelated place. I'm ok with removing it as long as this sort of protection is still available; if we change how the RecordUpdater is created/passed that will probably handle it.