asyn READBACK tag allows for waveform record to be updated whenever the
callback is called in code.

Without this, OPIs usually can't properly put or get to uninitialized
waveform records.

For user to be able to visualize what values are converted into
parameters.

Added enable/disable option, which now requires for all records to be
instantiated so we can properly communicate.

This particular IOC spits some error messages with the current test
setup because it only has two hybrids.

Added logging details to several functions. Also added log messages to
IOCMessage parameter.

As noted on st.cmd, instead of naming records <Device>:HybN we will name
them <Device><N>:<Property> (So the number is actually part of the
device).

So records with two digits refer to the whole IOC, records with three
digits refer to hybrid-specific parameters and records with four digits
refer to VMM3A specific parameters.

It was looking for parameter VMM_FEN_ACQUIRE but not finding it.
Now it can properly read the parameter, although it shouldn't be needed
to be read most of the times...

All parameters that share the same ADC are now added: Pulser, Threshold,
Temperature and Bandgap.

All except temperature are showing weird values though, so that needs to
be investigated. I suspect something to do with configHybrid or configFE
or configVmm, but I am not sure.

This reads Temperature from API memory and sets the structure for future
parameters such as BandgapADC, etc...

The timestamp is also read and put into a PV in order to be explicit for
user when was the last time it was read from hardware.

Now if API returns a bad status, asyn knows about it.

To use the correct term.

removed proof of concept. Made it work for all VMMs of all hybrids.

Turns out it wasn't that different from others. All it needs is to
change a bo record to ao.

Didn't add SD because the mechanism is a bit different.

This commit was done with an inescrupulous "git add ." after several
radical modifications.

Anyway, the API was radically modified and basically the old way the
code worked does not make any sense anymore.

The desired architecture is the following: the API is going to be used
as a class component. Each parameter will be created according to the
desired number of enabled hybrids.

Each parameter should use one simple API function. No information about
the VMM or hybrids itself is stored in the VMMTbl class unless extremely
needed.

This commit leaves a few old parameters that should be removed in the
future such as ADC_VALUE_VMM1, READ_ADC_VMMS, etc. This is only to serve
as a reminder to add those later.

Mostly just change names of files or classes.

If check is not made, ioc will try to write to register in the beginning and fail, crashing the application.

It wasn't supposed to be here. Should be named configFE only.

VmmTbl now inherits from asynPortDriver instead of FrontEndBase.
It has VmmTblAPI as a class component.

Thus, everything that used pRMM->foo(); such as pRMM->setStringParam(addr_list, vmmHybFwVersion_[hyb], pVMMConfig.readFwVersion(hyb).c_str());
are simply foor(); (equivalent to this->foo();)

Everything that used pVMMConfig.foo(); now uses pVmmTblAPI->foo();

configFEN had its name changed to configFE since the last configFE did
nothing.
Old configFE was removed.

In the end, findRegister() was not moved to VmmTblAPI because it seems
to be searching for a given register name based on an epics parameter.

vmm_config is now called VmmTblAPI. Following [Loki's example](https://gitlab.esss.lu.se/nice/dev-epics-modules/fe-r5560-loki/-/blob/include-api-on-module/r5560LokiApp/src/r5560LokiApi.h?ref_type=heads)
it inherits from RMM API's FrontEndBase, which means it doesn't need
pFEN as a class parameter anymore.

This breaks the whole application compilation, but it was already broken
in the new API structure.

It you compile only with

SOURCES += $(APPSRC)/VmmTblAPI.cpp

in the Makefile, it works. My intention is to keep adding the other
files now.

Other APIS follow the same structure. No need for a cpp file for this.

Substitution file is used in module build to set channel names, since that shouldn't change
too much with time and particular detector.

VMM and Hybrid numbers are left to be changed in the st.cmd file since that can change more often.

Now, for VMM, the pattern is:
$(R)$(H)$(V)$(C)$(CH)

R: Usually "NDet-VMMHYB-00". No colon after.
H: Hybrid number in range 0-5
V: VMM chip number in range 0-1
C: Colon Between device name and property Should be ":" but is a macro in case anyone
   decides that shouldn't be there anymore.
CH: Channel/register being set. Can be ST, SL, SC, STH, SM or SMX

Also, to make naming more visible and dynamic, stop using substitutions file.

Same as previous commits.
Basically add a list of EPICS parameters for each SMX channel and register, for each Hybrid-VMMChip pair.
List is indexed by Hybrid and VMM number.

Records are created with .sub file to avoid useless code repetition.

Nothing new, same stuff as the last previous commits.

This commit makes it possible to change all 64 SL registers for a given Hybrid-VMM pair.

The map keys are going to be used as register names
in the setRegister function, so they should be lowercase.

If for some reason findRegister cannot find what VMM and Hybrid should it operate into,
error message should help the poor soul who is operating IOC at the time.