[KOGITO-9265] Add the PodSpecTemplate to the SonataFlow CR

[ricardozanini]

Description of the change:
In this PR:

1. Complete refactor of controllers/profiles method. Now more clear and easier to maintain. Each profile has its own module and a common one to share features between them. Smaller names, funcs, and revisited structs. Unused code removed.
2. Since now the SonataFlow CRD is huge (thanks, podSpecTemplate!) we needed to change from kubectl apply to kubectl create in CRDs creation. I'll try to revisit the makefile since the deploy and install are trying to apply the same artifacts. The first one should only install the CRDs, the latter the other resources.

TODO:

• Reconcile the podSpecTemplate considering the specific user's custom template. Add guards to not override the controller's defaults like volumes, container name and etc.
• Unit tests
• Add a few custom attributes to the template in the e2e
• Documentation - [KOGITO-9265] Add PodSpec customization guide incubator-kie-kogito-docs#506

Motivation for the change:
See https://issues.redhat.com/browse/KOGITO-9265

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

[masayag]

For the SonataFlow status, when an image is specified, the condition states the following:

status:
  address: {}
  conditions:
  - lastUpdateTime: "2023-09-19T08:32:17Z"
    status: Unknown
    type: Built

Perhaps when an image is specified the status can be set to Obsolete or Skipped to highlight no build was executed by this flow.

[ricardozanini]

Usually Unknown is the convention, but I liked Skipped for this use case. I'll add it. :)

[ricardozanini]

@masayag what I did was Built = False, Reason: BuildSkipped. Can you give it a try?

[wmedvede]

I have left some comments in case it could make sense and some silly questions.
Thanks.

[ricardozanini]

@wmedvede I've made small changes to the API to reflect the PodTemplateSpec naming. Not sure why I inverted, might be a brain fart or due to discussions with @masayag. We used to call it that. @masayag wanna chime in about the naming change in the API?

Basically, we now have spec.podTemplate.container and spec.podTemplate for custom deployment changes. I think shorter is better.