feature: add support for hostAliases

[kfess]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR adds support for converting Docker Compose's extra_hosts field to Kubernetes' hostAliases field in Pod specifications.

When a docker-compose.yaml file contains extra_hosts entries, Kompose will now automatically convert them to the equivalent Kubernetes hostAliases configuration. This allows users to maintain custom host-to-IP mappings when migrating from Docker Compose to Kubernetes.

Which issue(s) this PR fixes:

Fixes #2066

Special notes for your reviewer:

• The conversion logic maps each extra_hosts entry (format: "hostname:ip") to a corresponding hostAliases entry with the IP and hostname
• Added unit tests to verify the conversion behavior

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kfess
Once this PR has been reviewed and has the lgtm label, please assign cdrage for approval. For more information see the Code Review Process.

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

Details

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

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten