Hot-fix: Add backoff/retry when requesting job status by id

Purpose

This PR adds a backoff/retry to our regression tests when requesting job status by ID.
This is required because it appears there is an existing issue with the WPS-T API.
- The issue is that when a request to execute a process is made, the response includes a 201 status code along with the job ID, however, if a request to get the job status is made immediately after the response is received, a 500 status code is returned. There appears to latency between when a job is said to have been accepted and when it is actually registered by the WPS-T.