Reset syncStatus for remote KB

Purpose:
Sometimes a remote KB can be left incorrectly with a syncStatus of 'in-process' rather than 'idle'. When this happens, the remote KB will no longer be harvested as when we check to see if we should run a harvest it seems that it is already running.

This story is to allow the user to recover from this situation by resetting the remote_kb syncStatus to 'idle'

User story statement(s):

As a ERM administrator
I want to be able to reset the syncStatus of a remote_kb
so that the next harvest will include the remote kb

Scenarios:

1. Scenario:
   • Given the Actions button on an External Data source record
   • When I click the Actions button
   • Then I see four options: Edit, Reset cursor, Reset sync status, Delete
2. Scenario:
   • Given the Actions button on an External Data source record
   • When I select Reset sync status
   • I see a confirmation dialogue
3. Scenario:
   • Given the Reset sync status confirmation dialogue
   • When the remote kb 'lastUpdated' status is less than 24 hours in the past from the current time
   • Then I see a warning: "The external data source was last used to update the knowledgebase <hours since lastUpdated time hours ago. It is only possible to reset the sync status from 24 hours after the external data source was last harvested"
   • I cannot reset the sync status but only Cancel the confirmation
4. Scenario
   • Given the Reset sync status confirmation dialogue
   • When the remote kb 'lastUpdated' status is more than 24 hours in the past from the current time
   • Then I see a warning: "The external data source was last used to update the knowledgebase <hours since lastUpdated time> hours ago. Only reset the sync status if you are sure the remote KB has incorrectly become stuck in an in-process state"
   • I can either "Cancel" the confirmation or reset the sync status to "idle" by clicking "Reset"

Dev task breakdown

• See dev task breakdown on ERM-1949
• Instead of directly wiring up the action button to the handler, we instead need it to open a confirmation modal.
• At that point we calculate time since "lastUpdated".
  • If >24h we display one message and a cancel/confirm button

• • • Cancel -> close the confirmation modal
    • Confirm -> use the submit handler
  • If <24h display other message and only cancel button
    • Cancel -> close the confirmation modal