Add Templates feature to foreman-proxy

[shubhamsg199]

Why are you introducing these changes? (Problem description, related links)

What are the changes introduced in this pull request?

• Enable templates feature for foreman-proxy

How to test this pull request

Steps to reproduce:

• foremanctl deploy --add-feature templates

Checklist

• Tests added/updated (if applicable)
• Documentation updated (if applicable)

[ehelms]

Does templates need to be in the features.yaml? I do not see how the feature in this PR ensures foreman-proxy gets added.

[shubhamsg199]

Does templates need to be in the features.yaml? I do not see how the feature in this PR ensures foreman-proxy gets added.

Yes, templates is declared in features.yaml under the foreman_proxy key (same pattern as bmc). I don't think we have a way to ensure if foreman-proxy gets added.

[shubhamsg199]

@ehelms Made some updates that ensures foreman-proxy gets added on the feature install. Not sure if that should be part of this PR.

[evgeni]

Do the changes to this file mean that if you do --add-feature templates on fresh, feature-less deployment, it will also enable the (base) foreman-proxy feature?

[shubhamsg199]

Yes

[evgeni]

I think that's wrong, this should be done by the user deliberately.

Especially, this means that enabling any other feature that has a proxy aspect will enable the proxy (like REX), if I am reading the code correctly.