Make sure Reggie works with BASE 3.3

[Nicklas Nordborg]

BASE 3.3 include a lot of JavaScript changes which may affect the functionality in Reggie. Before releasing a Reggie version for BASE 3.3, we need to verify that all wizards works as expected. Issues that are found should either be fixed as part of this ticket or (depending on the amount of work needed) a new ticket should be created.

The first step is to make sure that Reggie works with both BASE 3.2 and BASE 3.3 (assuming that Content-Security-Policy has been relaxed on the BASE 3.3 server).

If Reggie 2.15 is released before BASE 3.3 we don't have to worry about upgrading to BASE 3.3.

Only if BASE 3.3 is released before Reggie 2.15 we can consider taking advantage of new functionality in BASE 3.3.

There are already some tickets for taking advantage of new functionality in BASE 3.3.

• #515: Store sequence for barcodes as annotations on tags
• #539: Set "Disable log" flag on some annotation types
• #571: Update Reggie to new scripting pattern

[Nicklas Nordborg]

(In [2215]) References #540: Make sure Reggie works with BASE 3.3

Use Ajax.getXmlHttpRequest() instead of Main.getAjaxRequest() since the latter is being phased out.

Use function() instead of string in setTimeout since 'unsafe-eval` is not enabled in BASE.

[Nicklas Nordborg]

(In [2216]) References #540: Make sure Reggie works with BASE 3.3

Include main-2.js in protocol generation scripts or they will not work properly.

[Nicklas Nordborg]

(In [2217]) References #540: Make sure Reggie works with BASE 3.3

Remove calls to non-existing methods.