[BV-599] Write cluster metadata in a local file

[Franr]

What?

Write the K8S cluster data into a metadata file.

Why?

To facilitate the clusters discovery functionality.

References

• [BV-599] Kubeconfig helper leverage#281

[github-actions]

💰 Infracost report

Monthly estimate generated

Estimate details (includes details of unsupported resources and skipped projects due to errors)

──────────────────────────────────
132 projects have no cost estimate changes.
Run the following command to see their breakdown: infracost breakdown --path=/path/to/code

──────────────────────────────────
2598 cloud resources were detected:
∙ 596 were estimated
∙ 1881 were free
∙ 121 are not supported yet, see https://infracost.io/requested-resources:
  ∙ 45 x aws_identitystore_group_membership
  ∙ 37 x aws_identitystore_user
  ∙ 10 x aws_guardduty_member
  ∙ 7 x aws_identitystore_group
  ∙ 5 x aws_fms_policy
  ∙ 4 x aws_guardduty_detector
  ∙ 2 x aws_guardduty_organization_admin_account
  ∙ 2 x aws_guardduty_organization_configuration
  ∙ 2 x aws_organizations_delegated_administrator
  ∙ 1 x aws_cloudtrail_organization_delegated_admin_account
  ∙ 1 x aws_eks_access_entry
  ∙ 1 x aws_fms_admin_account
  ∙ 1 x aws_organizations_organization
  ∙ 1 x aws_route53_resolver_firewall_domain_list
  ∙ 1 x aws_route53_resolver_firewall_rule
  ∙ 1 x aws_route53_resolver_firewall_rule_group

_{This comment will be updated when code changes.}