status API: new entry to check for ambiguities if a set of new tags were to be deployed

[jbrzusto]

Given a data.frame of new tags (with columns tagID, manufacturer, model, codeSet, nomFreq, mfgID, period), check for any new ambiguities these tags would cause.

• use the code described in new function: build tag tables for find_tags_motus from motus-metadata-history commit hash #378 to build a temporary augmented tag database, using artificial
  motusTagIDs for the new tags

• run the tag finder with al new parameter --ambiguity_scan that scans through the event table building/tearing down the DFA graph while reporting any ambiguities caused by the new tags.

or

• write an R function to query the tags and events tables from the temporary database for each new tag, looking for ambiguities