Add test helpers to create and delete API keys

[labkey-tchad]

Rationale

Some tests need to have multiple remote API sessions open against servers that don't have database authentication enabled. In these cases tests should be able to log in via CAS then generate an API key that can create independent API connections.
We should also be able to delete the api keys to reduce clutter on remote servers.

With the large data involved in these tests, project deletion can exceed the load balancer/firewall timeout:

java.lang.RuntimeException: Failed to delete container: SampleStressImport
  at org.labkey.test.util.APIContainerHelper.deleteContainer(APIContainerHelper.java:169)
  at org.labkey.test.util.APIContainerHelper.doDeleteProject(APIContainerHelper.java:130)
  at org.labkey.test.util.AbstractContainerHelper.deleteProject(AbstractContainerHelper.java:151)
  at org.labkey.test.util.AbstractContainerHelper.deleteProject(AbstractContainerHelper.java:145)
  at org.labkey.test.tests.samplemanagement.perfandstress.DashboardReadsWithImportStressTest.doCleanup(DashboardReadsWithImportStressTest.java:38)
  [...]
Caused by: org.labkey.remoteapi.CommandException: Gateway Time-out
  at app//org.labkey.remoteapi.Command.throwError(Command.java:412)
  at app//org.labkey.remoteapi.Command.checkThrowError(Command.java:366)
  at app//org.labkey.remoteapi.Command.executeRequest(Command.java:352)
  at app//org.labkey.remoteapi.Command._execute(Command.java:321)
  at app//org.labkey.remoteapi.Command.execute(Command.java:185)
  at app//org.labkey.test.util.APIContainerHelper.deleteContainer(APIContainerHelper.java:156)

APIContainerHelper.deleteContainer should catch the 504 response from these cases and wait for the container to be gone.

Related Pull Requests

• https://github.com/LabKey/kanban/issues/359

Changes

• Add test helpers to create and delete API keys
• Allow APIContainerHelper.deleteContainer to handle 504 response

[labkey-danield]

Should this be an error condition?