This will be part of the artifact that will be published by the project. The other part, aside from sources, will be metadata necessary to compile them.

Currently, the task assumes that the SV source is in the conventional location. This will be fixed later to work in the general case.

This can only be done by creating the artifact from a `SoftwareComponent`. This actually has to be a `SoftwareComponentInternal`, however, otherwise Gradle will complain about cast errors in the Maven publishing code. Unfortunately we have to implement an internal API.

Defining custom components is possible using the public API: https://docs.gradle.org/8.6/userguide/publishing_customization.html#sec:publishing-custom-components.

The name of the variant is not configurable anymore. It's just going to be the name of the configuration we used to define the variant. This is not a big deal, as the name is not used anywhere, only its attributes matter.

We can add an example project that consumes this artifact once we implement that part.