Docker compose to devfile

[Mahajanet]

What does this PR do?:

This PR provides library support for a project with a docker-compose file in it while supporting existing containers, single service & Multi-service with no dependencies.
We are using Kompose and it's framework instead of using it as a CLI.
For the issue in reference, the testing for converting docker-compose references for inline, URI, and both absolute and relative URL cases is completed. The next steps would include:

1. Using the apply and deploy on the kubernetes components created
2. Cleaning up the temoprary folder created for the intermediate kubernetes representation
3. Unit Testing.

Which issue(s) this PR fixes:

This PR fixes the issue 1122, which is under the Devfile to Docker Compose Epic 501.

PR acceptance criteria:

Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened.

• Open new test/doc issues under the devfile/api repo
• Check each criteria if:
• There is a separate tracking issue. Add the issue link under the criteria
  or
• test/doc updates are made as part of this PR
• If unchecked, explain why it's not needed

• Unit/Functional tests

• QE Integration test

• Documentation

• Client Impact

• Gosec scans

How to test changes / Special notes to the reviewer:

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Mahajanet
Once this PR has been reviewed and has the lgtm label, please assign maysunfaisal for approval. For more information see the Kubernetes Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-merge-robot]

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[amisevsk]

Unclear from an initial reading of this PR, but is there a way to use docker compose support without relying on a filesystem? E.g. a way to pass in a devfile and get k8s components back out of it?

Something like

func convertDockerComposeToKubernetes(composeComponents []devfile.Component) ([]Client.Object, error) 

[amisevsk]

You could use the k8s.io/utils/pointer or k8s.io/utils/ptr package for this, e.g.

Suggested change

	ConvertDockerComposeToKubernetes: &trueFlag, //setting flag to true for parser
	ConvertDockerComposeToKubernetes: pointer.Bool(true), //setting flag to true for parser

[amisevsk]

In what cases is a replicationController to be used? My understanding is that a replication controller is an older way to have the functionality provided by deployments (+ replicaSets).

[amisevsk]

Consider breaking this up into multiple functions (e.g. a function for handling URIs), I'm finding it hard to parse with all the conditionals.