Fix backward compatibility

[McSim85]

Any versions before this PR #3762 (v6.22.1) use the main branch for requirements-lock.txt. (full url https://raw.githubusercontent.com/ansible/ansible-lint/main/.config/requirements-lock.txt)
It still uses the main branch even if you specify a particular version.
For example, this config

name: ansible-lint
on: [pull_request]

jobs:
  build:
    name: Ansible Lint # Naming the build is important to use it as a status check
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Code
        uses: actions/checkout@v2
      - name: Run ansible-lint
        uses: ansible/ansible-lint@v6.20.0

will try to download the main branch:

Run wget --output-file=.git/ansible-lint-requirements.txt https://raw.githubusercontent.com/ansible/ansible-lint/main/.config/requirements-lock.txt
  wget --output-file=.git/ansible-lint-requirements.txt https://raw.githubusercontent.com/ansible/ansible-lint/main/.config/requirements-lock.txt
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
Error: Process completed with exit code 8.

The PR that broke backward compatibility is this one #3925

Fixes: #3928

7fa5f76

[McSim85]

I basically made a symlink

➜  .config git:(main) ls -l | grep  requirements | grep lock                                                                                                                                                                                                                                              
-rw-r--r--  1 user  staff  1014 Dec  5 15:36 lock-requirements.txt
lrwxr-xr-x  1 user  staff    21 Dec  5 15:37 requirements-lock.txt -> lock-requirements.txt

[audgirka]

@ssbarnea I think, we should update the file name for wget to lock-requirements.txt instead of requirements-lock.txt.
As this is adding requirements-lock.txt and referencing lock-requirements.txt inside of it

[McSim85]

@ssbarnea I think, we should update the file name for wget to lock-requirements.txt instead of requirements-lock.txt. As this is adding requirements-lock.txt and referencing lock-requirements.txt inside of it

@ajinkyau
It's just a symlink. To be honest, I don't know why GitHub represents symlinks in that way:

adding requirements-lock.txt and referencing lock-requirements.txt inside of it`.

But if you pull my changes to your local machine, you will see it's a symlink:

$ .config git:(main) ls -l | grep  requirements | grep lock                                                                                                                                                                                                                                                 
-rw-r--r--  1 user  staff  1014 Dec  5 15:36 lock-requirements.txt
lrwxr-xr-x  1 user  staff    21 Dec  5 15:37 requirements-lock.txt -> lock-requirements.txt

note: requirements-lock.txt -> lock-requirements.txt

[McSim85]

Okey, this view represents better, what I just did
https://github.com/ansible/ansible-lint/tree/b366542caffa261d19a02d87d61731a477c7074c/.config