Summary and goal

Provisioning, an application that is integrated with Sources is being decommissioned, so we need to remove it both from the sources UI and the back end.

Also, Image builder wants to use Sources to store the cloud integrations that customers create through their wizard. However, they might not be ready to have availability checks implemented yet, so we might have to hide that feature for their specific cloud integrations/application combinations.

We are going to perform a safe "two-step" migration:

1. Create a new application type, and migrate all the old "Provisioning" applications that are tied to an AWS source to that application type.
2. Once the data is migrated in production, remove the old "Provisioning" applications along with their corresponding leftover sources and the dangling authentications, since the new "Image Builder" application will not require the old ARN authentication that was being saved.

Acceptance Criteria 

• Image builder can create "image builder" applications in Sources.
• Sources skips availability checks for image builder applications until told otherwise.

Checklist