Deprecate pulp_settings in favor of extra_settings

[Denney-tech]

SUMMARY

I think it would make sense for the galaxy-operator to behave more like the awx-operator for consistency's sake. This adds extra_settings: to the CRD and the settings.py.j2 template. I didn't see any data manipulation in the awx-operator roles, so I presume none are needed here.

ADDITIONAL INFORMATION

forum.ansible.com thread

Copied and modified documentation from awx-operator's extra_settings to here.

Depends on #98

[rooftopcellist]

@Denney-tech I definitely want something like this. But there are a couple changes I think we'll need:

• We should mark the existing pulp_settings parameter as "Deprecated" in the CRD and CSV. But we can't remove it because that would cause CRD schema conflicts within the same apiVersion (tl;dr, nightmares for upgrades)
• We will also need the templating logic to have backwards compatibility for pulp_settings.

[Denney-tech]

I added a deprecation warning in an assertion step, but not sure what to do about the CRD/CSV.

This is backwards compatible with #98, and I wasn't intending to remove pulp_settings entirely. I think pulp_settings should stay for a handful of releases and maybe set a target removal date.

[Denney-tech]

So, just to clarify since I'm a little green when it comes to k8s operators; we can't remove pulp_settings (or any other parameter) from a CRD unless we change the version, such as: galaxy_v1beta1_galaxy_crd.yaml#L15?

Does the CSV have to match the CRD? I don't see a similar version spec in the CSV.

[Denney-tech]

@rooftopcellist fixed the crd error, a mistake in the csv, and resolved the merge conflict that was present.

[Denney-tech]

Muddied the water a bit in my fork, so I'm closing these PR's while I cleanup.