HMS-5024: add use template modal

[rverdile]

Summary

Adds a "use template" button in the top left of the template details page that opens a modal with different sets of instructions on how to use templates.

Testing steps

[jlsherrill]

https://issues.redhat.com/browse/HMS-5024

[jlsherrill]

This looks great, a couple of things to mention:

1. For the first method, we probably should mention that subscription-manager refresh is needed after the steps which associates the system to the template
2. https://issues.redhat.com/browse/RHINENG-14351 is merged, so we can mention via the first method that you can use the UI to associate the system OR use this new api:

PATCH /template/$TEMPLATE_UUID/subscribed-systems  

but we could fill in the $TEMPLATE_UUID with the actual UUID. I haven't tested this yet to confirm it works, i can do that on monday. So it could just show the curl command which trigger the association.

3. for the curl and ansible method, we probably want to mention that system advisory information will not be available via the patch application

[rverdile]

updated and updated the screenshots

[swadeley]

/restest

[swadeley]

/retest

[jlsherrill]

I think there should be a space between these two buttons:

For the curl and ansible tabs, could you add an alert/warning box with something like:

Consuming a template in this way will result in the system not reporting applicable errata properly within Insights.  

[rverdile]

updated!

[jlsherrill]

Apologies i didn't think about this prior, but one small adjustment, now that "Patch" isn't actually a navigation item, it may make more sense to say "System advisory information will not be available via Systems" and have Systems be a link which links to /insights/patch/systems

IDK that users will necessarily think of "Patch" as an application now that it doesn't have a nav entry.

[jlsherrill]

everything else looks great!

[rverdile]

updated!

[swadeley]

Hi

buttons have space between them:

the three tabs:

Insights:

curl:

Ansible:

[swadeley]

Hi @jlsherrill

URLs are hardcoded I take it, no stage or ephemeral support then. OK?