feat: alloy installation via repository + suse support

[pkretzer]

• Added variables to install the alloy agent via a repository or url (defaults to url).
• Added support for installing on openSUSE
• Added molecule configuration for testing.

[CLAassistant]

All committers have signed the CLA.

[ishanjainn]

@voidquark any thoughts on this?

[voidquark]

will check this

[voidquark]

Hello, Thanks for contributing! 🚀

Here are my findings and some missing pieces:

• When using the repository, the latest version is always installed. This might not be what users expect when they specify a particular version.
• The README definitely needs documentation for the new variables.
• I don’t think it's necessary to modify the Molecule file since the supported distros are already listed here.
• I'm also not sold to idea that repository management should be part of this role. It make sense to support installation via the repository, but I believe managing the repository itself should be outside the scope of this role.

Why I think the repository should be managed separately:

• You can handle repository management in your pre_tasks or with a dedicated role that manages repositories system-wide.
• Alloy Uninstall tasks and removing the repository is risky. What if the repository was set up differently and is now unexpectedly removed? The purpose of uninstalling should be to clean up the role’s resources, not system-level resources like repositories.

Therefore, I believe this PR should be adjusted to:

• Include possibility to install package via the repository.
• Allow users to select a specific version for installation via the repository.
• Make it clear in the README that this role does not manage the repository itself. The repository must already be present on the system.