Feature Request: Expose alloy version in configuration

[adlotsof]

Request

Analogue to the constants, ideally as part of the constants https://github.com/grafana/alloy/blob/main/syntax/internal/stdlib/constants.go, it would be extremely helpful to be abled to access the version of the alloy binary in the configuration.
For now, to archive this, setting an environment variable and retreiving the environment variable using sys.env() would be one option, another one would be to hardcode the version in the configuration file.

When using import.http to retreive configuration files from a central repository which receives constant updates, it would be much easier to manage the usage of new features and syntax elements if it would be possible to align the configuration files with the correct alloy version.

Looking at the code briefly, it seemed like an easy change (simply add the version to syntax/internal/constants.go). When looking more closely, it seems like this would cause a circular import and would not work.

Use case

managing 100s of alloy deployments with remotely stored configuration modules, to align the version of the modules with the version used in the deployment.