Refactor Ray and AppWrapper modules

[Bobbins228]

Issue link

Closes: RHOAIENG-13332

What changes have been made

Refactored the Ray and Appwrapper modules to fit the design doc

Verification steps

E2E and Unit tests should be sufficient

Checks

• I've made sure the tests are passing.
• Testing Strategy
  • Unit tests
  • Manual tests
  • Testing is not required for this change

[varshaprasad96]

The split looks good overall! 👍

[ChristianZaccaria]

Ran through an imports diagnostic tool, looks great! - Just left one comment

[ChristianZaccaria]

/lgtm

[KPostOffice]

Is this a breaking change @varshaprasad96 ? Do we need to maintain the current imports for a few releases?

[varshaprasad96]

Do we need to maintain the current imports for a few releases?

This is a breaking change, but we are going to continue to support the API functionality as is - so it should not be a requirement to maintain the import paths. Specifying in the changelog and mentioning it in the documentation should be enough.

[KPostOffice]

Do we need to maintain the current imports for a few releases?

This is a breaking change, but we are going to continue to support the API functionality as is - so it should not be a requirement to maintain the import paths. Specifying in the changelog and mentioning it in the documentation should be enough.

Heard that. I wasn't sure if we had any obligations for it to be exactly the same import path. I'm good then

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: KPostOffice, Ygnas

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [KPostOffice]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

resolved