Removed k8s client go dependencies from graphql

[Saranya-jena]

Proposed changes

Removed k8s client go dependencies from graphql server. This enables us to restrict the scope of what graphql server can do regarding interactions with hosts and other system backend services(i.e. k8s). As part of the change, the host IP is now extracted from the HTTP header thus removing the requirement if using client-go to find out the endpoint.

Summarize your changes here to communicate with the maintainers and make sure to put the link of that issue

Types of changes

What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

• New feature (non-breaking change which adds functionality)
• Bugfix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices applies)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have signed the commit for DCO to be passed.
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

Dependency

• Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer:

[shovanmaity]

LGTM

[Jonsy13]

We can add Dex config back in both manifests