Feature: Registry for drivers and expose driver info in CLI

[unsuman]

This pull request introduces a driver registry for internal and external drivers and exposes driver information through the CLI. This change is a critical step towards a full plugin architecture, enabling the discovery of external drivers.

Key Changes

• Driver Registry Implementation: A new pkg/registry package has been introduced. This package is responsible for discovering and managing available drivers, creating a centralized system that allows Lima to dynamically identify built-in and external driver plugins.
• Exposure of Plugin Info in limainfo: The limainfo data structure is now updated to include metadata about the driver whether it is built-in or external(with the location of the binary).
• CLI Enhancements: The limactl command-line tool has been updated to leverage the new registry and limainfo fields. Users can now view the available drivers through limactl create --list-drivers.

GSoC Context

This is the 2nd of 4 PRs in the initial GSoC project submission. It is dependent on the merge of the #3691 and serves as a necessary prerequisite for the two remaining PRs to be merged.

Related Issues

• Closes Implement Central Registry for Built-in Plugins #3549
• Closes Expose Plugin Information in CLI #3552

[alexandear]

Could you add unit tests for this newly created package?

[unsuman]

May I add it under #3554 and another PR because it will require a mock diver and Register() function(see this) in order to test functions like Get(), registerDriverFile() etc?

[alexandear]

I guess we can simplify (but I'm not sure without any tests):

Suggested change

	if !strings.HasPrefix(base, "lima-driver-") {
	return
	}
	name := strings.TrimPrefix(base, "lima-driver-")
	name, ok := strings.CutPrefix(base, "lima-driver-")
	if !ok {
	return
	}

[AkihiroSuda]

Thanks, I'm merging this, but please take a look at the review comments