Cherry-pick #18912 to 7.7: Fixing type of ingress_hostname

[kaiyan-sheng]

Cherry-pick of PR #18912 to 7.7 branch. Original message:

Type of change: Bug

What does this PR do?

See issue: #17192
It changes the type of the ingress_hostname field since it is not an IP address

Why is it important?

It is causing mapping issues (ingress_hostname is not an IP address): #17192 (comment)

Checklist

• [x ] My code follows the style guidelines of this project
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have made corresponding change to the default configuration files
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Please let me know if I'm missing something here and I should have done anything else.

Related issues

• Closes Metricbeat mappings  #17192

Other types seem fishy too (should be IPs?), please let me know if you want these to be fixed too in this PR:

    - name: external_ip
      type: keyword
      description: Service external IP
    - name: load_balancer_ip
      type: keyword
      description: Load Balancer service IP
    - name: ingress_ip
      type: keyword
      description: Ingress IP

Logs

See: #17192 (comment)

{
  "type":"mapper_parsing_exception",
  "reason":"failed to parse field [kubernetes.service.ingress_hostname] of type [ip] in document with id 'abc123'. Preview of field's value: 'xyz123.elb.us-west-2.amazonaws.com'",
  "caused_by":{
    "type":"illegal_argument_exception",
    "reason":"'xyz123.elb.us-west-2.amazonaws.com' is not an IP string literal."
  }
}

[elasticmachine]

Pinging @elastic/integrations-platforms (Team:Platforms)

[blakerouse]

Backport looks good