The requirement for the location of dotnet dependencies in `config.sh` seems overly strict

[linghengqian]

Describe the bug
A clear and concise description of what the bug is.

• The requirement for the location of dotnet dependencies in config.sh seems overly strict. To solve this problem, I always need to cd ~/actions-runner. This makes installing Actions Runner on the host machine more cumbersome than installing it in a Docker container.

To Reproduce
Steps to reproduce the behavior:

1. Run the following command on Ubuntu 24.04.

cd ~/
mkdir ~/actions-runner
curl -o /tmp/actions-runner-linux.tar.gz -L https://github.com/actions/runner/releases/download/v2.334.0/actions-runner-linux-x64-2.334.0.tar.gz
tar xzf /tmp/actions-runner-linux.tar.gz -C ~/actions-runner/
rm -rf /tmp/actions-runner/actions-runner-linux.tar.gz
sudo ~/actions-runner/bin/installdependencies.sh
~/actions-runner/config.sh --url https://github.com/some-org/some-repo --token SOMETOKEN

2. See error.

ldd: ./bin/libcoreclr.so: No such file or directory
ldd: ./bin/libSystem.Security.Cryptography.Native.OpenSsl.so: No such file or directory
ldd: ./bin/libSystem.IO.Compression.Native.so: No such file or directory

Expected behavior
A clear and concise description of what you expected to happen.

• The requirement for the location of dotnet dependencies in config.sh should be optimized. In other words, I don't think cd ~/actions-runner is necessary.

Runner Version and Platform

Version of your runner?

• https://github.com/actions/runner/releases/tag/v2.334.0

OS of the machine running the runner? OSX/Windows/Linux/...

• Linux

What's not working?

Please include error messages and screenshots.

• It doesn't seem important.

Job Log Output

If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.

• It doesn't seem important.

Runner and Worker's Diagnostic Logs

If applicable, add relevant diagnostic log information. Logs are located in the runner's _diag folder. The runner logs are prefixed with Runner_ and the worker logs are prefixed with Worker_. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.

• It doesn't seem important.