[question] Confusion on ASDF_INSTALL_PATH and ASDF_DOWNLOAD_PATH

**Describe the bug**

First of all thanks a lot for the great tool, I'm happily using it since years now 🙂

Using this template as a base I'm trying to develop a plugin for [Kiota](https://github.com/microsoft/kiota).
The current version is here: https://github.com/andreaTP/asdf-kiota

To get things working I have had to craft the script to sanitize the paths passed by the env variables, done [here](https://github.com/andreaTP/asdf-kiota/blob/f046524c34c34f153c63c204d99b76cce5d935df/lib/utils.bash#L73-L78).
Unfortunately, this doesn't (probably) play nicely with the GH actions that are still failing.

Without the mangling, the variables are looking pretty strange, e.g.:
```
ASDF_DOWNLOAD_PATH=/Users//.asdf/downloads/kiota/https://github.com/microsoft/kiota/releases/tag/v1.1.3
```

Here I'm asking for guidance on how to proceed to fix the CI and possibly follow best practices in the plugin development.
Thanks in advance!

Start with the ASDF_INSTALL_PATH and ASDF_DOWNLOAD_PATH usage described in the issue and inspect the referenced lib/utils.bash path-sanitization code. Then reproduce the failure in the plugin's GitHub Actions checks and compare the behavior with the asdf plugin template. Done means the path contract is clarified and CI passes without relying on incompatible path mangling.

Written by the indexing model from the issue text.