v1 tag not pointed at the latest v1 release

We ran into this issue because we were getting deprecation warning for node v20 as was fixed in https://github.com/allure-framework/setup-allurectl/issues/139 back in May, however because we followed the docs and installed using this code:

```yaml
- uses: allure-framework/setup-allurectl@v1
```

We only got the v1.0.0.

I think it's common practice to either bump the v1 tag on each release of v1.x or (maybe) even github does this automatically if there is no v1 tag in the repo. Either way the tag points to the original v1.0.0 release: https://github.com/allure-framework/setup-allurectl/tags

Start by inspecting the repository tags and the documented `allure-framework/setup-allurectl@v1` installation reference, then compare the v1 tag with the latest v1 release and issue #139. Done means the v1 tag resolves to the latest v1.x release so the documented GitHub Actions usage receives the fix.

Written by the indexing model from the issue text.