update csp-lmc-common and mid-csp-lmc versions.

use lmc-base-classes version > 0.5.2 that requires ska_logging >= 0.3.0

Some refactoring of the Configure method to resolve the
bug of configuration failure after and EndScan command:
- if subarray is READY when Configure is issued, put a delay to wait
  for CONFIGURING transition (temporary hack)
- added check on scan configuration string: if is equal to the
  last valid configuration programmed, the configuration step is
  skipped (the subarray is already programmed)
- if failure/timeout during configuration, check if the failed
  device is the CBF subarray.
- decorators for Configure method are applied in the mid/low instance
  code.
Updated the tests.

ska-logging < 0.3.0

Removed a bug in CspSubarray.
Specified the ska-logging version to resolve
a problem with SKA Base classes (ska-logging package changed import
style while lmc-baseclasses still use the old one).
Use pytest-forked to run tests.

    with linting test)

with linting test)

Issues when the root attribute is a TANGO Spectrum of DevString (free problem).
Moved REceptorsMonitor device to VCCsMonitor device.
Updated json config file for CSP.LMC Common and Mid.CSP.LMC.
Added tests to read the addresses of the Capabilities devices.

Removed some typos.
Updated history and release files.

CspMaster monitoring thread.
Reduced the sleep time inside the thread function (from 1 to 0.1 sec).
Removed the callback registration with the asynch commands.
CSP State update is updated inside the event callback only when the CSP
is not running power commands.
Updated HISTORY, release and conf.py files.

during tests execution.

CspCapabilityMonitor.py: unsubscribe events and cleaning of the
event list on device deletion.
Removed linting bugs.

the decoupling of the mid-cbf-mcs and csp-lmc devices during test execution
(TmCspSubarrayLeafNode does no more subscribes on the CspSubarray
forwarded attribute outputLink but directly to the CbfSubarray
attribute outputLinksDistribution)

projects.

It fails n random way. Need to look at this case carefully to understand
the origin.

the decoupling of the mid-cbf-mcs and csp-lmc devices during test execution
(TmCspSubarrayLeafNode does no more subscribes on the CspSubarray
forwarded attribute outputLink but directly to the CbfSubarray
attribute outputLinksDistribution)

produce the metrics for the projects of the repository.
Not yet resolved the issue relatated to the combination of the
coverage generated by different projects hosted in the same repository.
Tried to use relative paths in vocerage (option [coverage:run] relative_files = True
in setup.cfg) with no success.

csp-lmc-common project.

perform in the proper way the Mid.CSP subarrays.
Changed name to the Mid.CSP TANGO DB volume.
Update dsconfig file and release number.

Removed tests to switch-off the CSP.
Updated release number.

Change to .gitalb.ci.yml (removed only changes on source files)

Some changes to linting configuration.

to reflect the new TANGO attributes added in the CspMaster parent class.

AT5-382: modified  Dockerfile and setup.py to install the package in editable mode with its dependencies.

Update release information.

install the package in editable mode with its dependencies.

Moved logger.warn (deprecated) to logger.warning
CspMaster: moved attribute with "alarm" string in the name to "failure".
Removed the default polling for xxCmdDurationExpected/Measured attributes.
Removed a bug in the Off() method: final state was cheked against ON.
CspSubarray: removed severe errors from the delete_device() method.
Commented out the line with connection to PssSubarray.
Removed a bug in passing arguments to the SubarrayRejectDecorator.

Removed the start of the PssMasterSimulatorDevice.
Updated the csp-lmc-common TANGO DB configuration to resolve
forwarded attributes not addressed.