FU: Check for "filename" also for UKIRT & keep the file entry ...

... else Astro::FITS::HdrTrans fails for not finding a header translation class.
Mind that deleting the "file_id" (JCMT) entry did not have this bad effect.
FU: Whitespace changes.
Translator-test: update reference RxWD status

The status of channels A and B has been swapped.
Translator-test: update reference seeing headers
client: observed script omits JSA for UKIRT

There was already a block of text for WFCAM which was similar to the
JCMT text but with the mention of getting reduced data from CADC
removed.  This commit selects this block for all UKIRT projects.
OMP::MSBDB: trap error in query's first HA calc/n

Commit d11124fbad introduced an eval block around the observability
test because errors raised by the modules performing that test
would cause the entire query to fail.  Subsequently commit
ac0faf2586 added HA calculations to the query in order to determine
whether or not a constraint test at transit is required (for the
purpose of checking whether SCUBA-2 observations exceed the
maximum elevation).  This introduced another point at which the
query can fail due to co-ordinate calculations, as happened
recently when an MSB was inserted into the database with an
observation which had TLE coordinates containing an unreasonable
epoch year parameter.  (Astro::Coords::TLE has meanwhile been
updated to reject epoch years which would result in negative
UNIX times.)

This commit wraps that new HA calculation in an eval block
to trap errors at this point.  The calculation could not simply
be moved inside the existing eval block because that is only
executed if the observability constraint is enabled.  There
are other calculations which could also fail, but if the
coordinates are bad it is quite likely that this would be
detected in the HA calculation.  It is tempting to place
the whole "$delta" loop in an eval block, but it is also the
case that if there are problems then we would like to
know about them.  Perhaps the ideal thing would be for the
MSB query to be able also to return a list of the MSBs
for which errors were encountered, preventing their consideration.
OMP::MSBDB: check TLEDB when inserting AUTO-TLEs

When storing AUTO-TLE coordinates in the ompobs table, the omptle
table is now searched for the given target.  If present then the
coordinates from the omptle table are copied to the ompobs table
(still with coordstype set to AUTO-TLE).  This commit is complicated
by the database not allowing two active statement handles, so we
must destroy the prepared ompobs insert statement handle before
querying the TLE table and then re-prepare it afterwards.
client: delete observe_backup_msbs script

This script has moved to the OMP Python repository.
Merge branch 'master' into summit