Make /report/ url compatible with a legacyid

[whatisgalen]

ResourceInstances are saved with a resourceinstanceid uuid and an optional string legacyid. This report view url could support a query parameter that takes a legacyid string in lieu of a uuid:

/report/1234-abcd...
/report/?legacyid=myLegacyID_with/certain-special!characters

When you import data via csv importer, for example, if you designate a column of non-uuid strings as "use as an id", then presumably those legacyids might be how you primarily identify your resources, especially if the name is intelligible/follows a naming scheme. Additionally, in order to know which resourceinstanceid uuid corresponds to which row in your csv, you'd have to re-export the data and do a lookup against it into your original file.

The drawback to the example approach is that certain characters would be prohibited for legacyid strings, e.g. ?#&%= at a minimum. My guess is that these are rarely used in legacyids anyway.