seperate jx installation from cluster creation

[rochana-atapattu]

We can use custom or predefined cluster for jx installation #225 . Here I have extracted the JX related code from GKE related code so that we have the option to install JX to exsisting cluster.

[jenkins-x-bot]

Hi @rochana-atapattu. Thanks for your PR.

I'm waiting for a jenkins-x or todo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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 jenkins-x/lighthouse repository.

[jenkins-x-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign msvticket
You can assign the PR to them by writing /assign @msvticket in a comment when ready.

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

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

[roulettedares]

This seems like a good idea. I believe that this should be a nondestructive/safe change for downstream users of the module since the google_container_cluster object itself remains in the same path at module.cluster. @rochana-atapattu have you tried to apply the new module logic to an existing cluster?