Testing of Tango alarm handling

Covert into a Spike based on CS Guidelines section 5.10 to bring this up to date.

HISTORIC Description below:

For PI10 this ticket is focused on testing since the Alarm handling has been integrated 

Earlier info retained for historical context

------------------------------------------

Elettra Alarm Handler has been finalized for use in SKA Tango implementations due to its advanced features.

This has been tested in at least a partial way through the early versions of TMC /MVP.

However it is required to

1. revisit the latest versions updated by the community,

2. especially explore the possible integration with Panic and check maturity for implementation as a package 

3. Based on the maturity implement packaging

Docker image etc for use by other components /LMCs 

Some of the capability to check for this first basic alarms handling packaging could include the following. This is a suggested list and can  be modified based on what is actually supported by the currently updated Elettra alarm implementation :

• reacts to threshold crossing of a TANGO attribute value,
• reacts to acknowledgement by the user,
• displays an alarm list, showing the following alarm attributes:  alarm message, alarm state, alarm priority, alarm type, alarm setpoint (as stretch: TANGO attribute value that cause alarm to be triggered, time and date of occurrence of the alarm state change),
• implements alarm states NORM, UNACK, ACKED, RTUN (for now omitting SHLVD, DSUPR, OOSRV),
• with configurable alarm rule (vs encoding of rule using a programming language).

This list originated from this discussion document (which also contains links to documents that define, for example, the alarm states mentioned above):  https://docs.google.com/document/d/1ckBcvv8KsUyafuoGIma4LrJAgSh_VF8HjvTAFTJ_poc/edit?usp=sharing_eil&ts=5d3eaf89 

Packaging and deployment will be a key aspect of this feature