Add support for collecting instance IP address

[songponssw]

What does this PR do?

• Fix Report VM IP addresses to host agent #3616
• Adds support for generating an instance instance_info.json file.
• This file includes basic instance information: name, IPv4, and IPv6 addresses.

Implementation details

With GuestAgent:

• The raw output from ip -j a is embedded as json_bytes in the gRPC Events message.
• The GuestAgent listens for this event, extracts the IP information, and writes it to the instance_info.json file.

Without GuestAgent (Plain mode):

• This PR updates the executeSSH() function signature to return both the command output and error (instead of just error).
• After completing any requirements setup, HostAgent uses executeSSH() to run ip -j a, processes the output, and writes the instance info locally.

Testing

• Setup: Lima upstream master, OS(Ubuntu 22.02)
• templates: almalinux alpine debian fedora opensuse oraclelinux ubuntu
• Test command: limactl start INSTNAME --network lima:user-v2
• Result
  • With GuestAgent: All tests passed.
  • Plain Mode: Failed on AlmaLinux and Alpine — instances did not start successfully.

[songponssw]

Changes – Draft 2 (edited)

gRPC

• added CommandOutput message to hold output from the client.
• Created dedicated endpoints for GetIPv4 and GetIPv6.

Hostagent

• agent get ipaddress as the last step in host agent routine and it should all only when the instance spin up.
• Stores IP addresses internally
• Exports IP address through the Info strut in hostagent/api

CLI

• Added IPv4Address and IPv6Address fields
• IP address are now available, e.g.: limactl ls --format "{{ .Name }} {{ .IPv4Address }}"

Note;

• IPv6 is currently unavailable; no default route is found.
• gRPC compiled grpc with protoc-compiler 6.30.2

P.S. I'm trying my best to follow the design patterns found in the existing code. If there are any points that need refactoring, please let me know.

[AkihiroSuda]

I still think that the IP can be added here without wrapping it in CommandOutput

#3616 (comment)

[songponssw]

I’ll try adding the IP address directly to RPC and remove all CommandOutput wrapping

[songponssw]

Edit:
I had a bit of confusion. I thought we were trying to use net.Interface() as a way to query the IP address.
I’ll continue making the changes according Akihiro's comment

# PR Update (draft3)

## Details
- supports only IPv4.
- Hostagent requests the guest for its IP through RPC.
- IPv4Address is added to Hostagent Info, so it can be shown when using curl on ha.sock at http://$INST/v1/info.

## Determining the IP Address
- The IP is determined by finding an address that can dial lima.host.internal.
- net.Interfaces() returns a list of all interfaces on the machine. I’m not sure whether there will be only 2 interfaces in practice (loopback and primary interface). If that is the case, the implementation could be simplified to pick the primary interface from the list.

## Not sure how to implement it yet.
Support IPv6:
- With the current implementation, we would need an IPv6 address for host.lima.internal.
- Otherwise, we could assume it uses the same interfaces as IPv4 or dial another destination such as Google DNS or Cloudflare.

Support Plain Mode:
- If we want the same implementation to work for both normal and plain mode, we might need to transfer a small binary to the VM to execute and report the IP via RPC.
- I’m not sure if we can reliably get the IP during VM initialization. This might limit the ability for the client to edit the IP after creation. (I’m not quite sure yet exactly when and how IPs are assigned)
- In plain mode, there is no lima.host.internal in /etc/hosts. We would need to dial another destination to figure out the default route.