refactor: use a metadata file for forges

[roele]

This is a follow up on #1905 attempting to move the "un-dirname" logic out of the ForgeArg into the Forge implementations.

Additionally it seems for Go while package names cannot have -, module names can and often do. So the logic for Go will also not work reliably. For example https://pkg.go.dev/search?q=http reveals all sorts of exceptions.

Using a + as separator would yield better results but i'm afraid thats not easy to change now is it?

[jdx]

I think we need to modify our strategy. Maybe we need a metadata file to store the real name

[roele]

Agreed, the path is not suitable and will most likely continue to cause problems no matter what separator we use.

[jdx]

I think it's worth doing though. For example, I bet mise upgrade probably needs this in order to work. I'm not sure if I've tested that with these yet or not.

[roele]

Gave it a first shot but i'm not sure if we should use a structured file instead? Also the upgrade does not seem to work for all backends but i'm not sure if this is related or is caused by something else yet.