Action fails with gitea/forgejo actions

I am trying to use the action in Gitea/Forgejo actions, and it fails like so:

```
⭐ Run Main ./setup-asdf-tools
☁ git clone 'https://github.com/asdf-vm/actions' # ref=v4
⭐ Run Main Install asdf & tools
🐳 docker cp src=/var/lib/gitea-runner/.cache/act/asdf-vm-actions-install@v4/ dst=/var/run/act/actions/asdf-vm-actions-install@v4/
🐳 docker exec cmd=[node /var/run/act/actions/asdf-vm-actions-install@v4/install/main.js] user= workdir=
❗ ::error::Action failed with error HttpClientError: Bad credentials
::error::Action failed with error HttpClientError: Bad credentials
❌ Failure - Main Install asdf & tools
⚙ ::set-env:: ASDF_DATA_DIR=/root/.asdf
⚙ ::set-env:: ASDF_DIR=/root/.asdf
⚙ ::add-path:: /root/.asdf/bin
⚙ ::add-path:: /root/.asdf/shims
```

It looks like it tries to talk to _github_ to install things, using a token (is it needed ?)

Trying to export a `GITHUB_SERVER_URL` env var didnt change anything in my case (I tried int in case it was something with the actions SDK).. Gitea actions provides a GITHUB_TOKEN that is valid on the instance, and the api for that is compatible, so I think the action is talking to github directly and not to my instance.

```
- run: echo "GITHUB_SERVER_URL=https://git.[REDACTED]" >> $GITHUB_ENV
```

Any advice on how to make it work ?

Start with the install/main.js entry point shown in the action log and trace how the action selects its API host and credentials. Reproduce the action in Gitea or Forgejo, then verify that installation completes using the instance's compatible API and token without contacting GitHub directly.

Written by the indexing model from the issue text.