Enhance workflow for creating a private probe

[ckbedwell]

Problem

The workflow for setting up a private probe is somewhat nonsensical at the moment, especially when reading it combined with the documentation. The steps feel out of order and certain information is presented that you don't know you need until you get to a later point in the setup process.

Acceptance criteria

Please rework the private probe creation process to have an enhanced UX and more intuitive workflow. The documentation will also need updating. Proposed workflow:

1. Click new private probe
2. Fill in probe details
3. Indicate the purpose of the map (it is not clear at the moment and not necessarily important so move where it is in the workflow)
4. Click 'Add new probe'
5. Either make the modal undismissable until explicitly clicked on a dismiss method (e.g. not the overlay but a close button) or add the information on page.
6. Display both the access token and the api server (hardcode the mapping to the application) explaining both will be needed when setting up the probe.
7. When viewing the new probe on the edit probe page, display the api server alongside the reset access token
8. Add a test probe button which utilizes the adhoc functionality.

Please ensure whatever solution is implemented has the appropriate integration tests added.