Ensure renaming function parameter is compatible change for the compiler plugin

[koperagen]

We need a new @ParameterName annotation that has priority over regular name, and serves as compatibility in case of rename.
So let's say plugin expects fun explode(selector), we want fun explode(columns), so we should

1. Rename parameter and add a annotation explode(@ParameterName("selector") columns)
2. Create a new interpreter that expects "columns" name, so we could eventually migrate

With that said, this mechanism will work starting from 2025.3 as we can't get this change in 2025.2 release. So for now we should not rename parameters

[Jolanrensen]

We should probably also introduce some versioning somewhere. We should think about the case where the compiler plugin is older than the library ánd where the library is older than the compiler plugin.

[koperagen]

compiler plugin is older than the library

In this case versioning can be done like this:
if we make an incompatible change, we can bump interpreter id => plugin doesn't know about this function and won't give an incorrect result.

the library is older than the compiler plugin.

Providing we have separate interpreter id for functions, we can keep older interpreters in the plugin