[ENSCORESW-720] and [ENSCORESW-721]. Allowing default HashRef in execute() and sleep for less than a second.

First issue raised by Lee from EG. He wanted to be able to work with hash refs
in the same way you can do with ArrayRefs. Done and dusted.

Second issue raised by me. Want to sleep for periods less than 1 second for the test
suite sanity.

Rose ORM framework.

Add 'HAP' to the list of types of patches to project so that the haplotypes sequence mappings and karyotype bands won't be missed again.

that should not happen, but non-species database will not have a version
this includes ancestral sequences databases

we now have a display_name meta_key, added method get_display_name

Patch submitted by Yuri Delia as aliases were added into the registry
even if a database was not found e.g. ontology. Additions moved
into the if blocks when we find and DB and constructed its adaptor.

Reverted Production DB dependency in order to allow Xref pipeline to run. Changes can be reinstated once slightly more mature.

The code did not attempt to build the additional lookup before fetching from
it. Our solution is to switch to requesting the cache in get_????_additional_lookup()
which will trigger the building of the additional lookup.

[ENSCORESW-577]. Fixing a logical hole where we reqiured a method to be defined but did nothing with it.

Looks like I was between implementations. Now switched to requesting the
additional lookup keys and if the hash was empty then skipping
any additional work. Seems to behave a lot better and means users need
only override one method in the object.

(ie, include the duplicated sequence Y has in common with X rather than the two sequences unique to Y)

DensityType is not a feature but is the object storing the analysis related
to the DensityFeature

unlike other features, the related analysis is stored in the density type table

added test for 'fetch_all_by_feature_class' with density features

Other schemas may need this which do not go through a process of removing
old/retired seq region ids in favour of their new ids. When querying by a slice
this is automatically delt with. When fetching by an ID you now need to
force the search on.

Fixed a warning that was testing the wrong value and failing to verify a store_alt_alleles call properly

It seems that $DBI::errstr has a very strange life. We can get the error message
recived by incorrect connections or bad drivers (DBD::mysql is missing) when we
just warn the error. However concatenating it into another string makes the
message disapear. Even assignment and then concat will not work. Instead we
have switched to using the $@. This has the error in it.

The optimise tree step can take a very long time and cause web timeouts. We have
added a time limit expressed in floting-point seconds. If an optimisation is
taking longer than the specified time we will abort any more attempts.

The optimise tree step can take a very long time and cause web timeouts. We have
added a time limit expressed in floting-point seconds. If an optimisation is
taking longer than the specified time we will abort any more attempts.

The original code decalred a max of 2K ids because of max allowed packet concerns
and wanted the packet to stay close to 256KB. However the actual figure was off
by a factor of 8 as the max packet is 1MB not 1Mbit. We have increased the limit
to 16K when working with numerics. Strings are still at 2K due to their possible
large size.