Update Transformer code to use configurable Ignite Service Token

Type of change

• Bug Fix
• Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

• Resolves #244 (closed)
• Resolves #245 (closed)

Does this introduce a change in the core logic?

• [YES/NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• GCP
• IBM

Does this introduce a breaking change?

• [YES/NO]

What is the current behavior?

• Ignite Service Token for K8S Profile leverages default /var/run/secrets/kubernetes.io/serviceaccount/token
• Provider Ignite Host/Port is determined only by what is set in the koop-config.json file

What is the new/expected behavior?

• Ignite Service Token can now optionally be set different than the default by populating the environment variable GCZ_IGNITE_SERVICE_TOKEN
• Provider Ignite Host/Port now optionally supports configuration via Environment Variables GCZ_IGNITE_HOST and GCZ_IGNITE_PORT

Have you added/updated Unit Tests and Integration Tests?

NA

Any other useful information

These small features contribute toward the overall configuration flexibility for production/K8S environments.