Small update to README_RELEASE_PROVIDERS.md

[vincbeck]

I ran the PMC checks for provider release for the first time and I found some two very minor glimpses in the doc.

• breeze release-management check-release-files providers requires the --path-to-airflow-svn parameter
• The parameter --packages-file should contain the reference to the packages.txt file from the Airflow root repo and not the current directory.

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[potiuk]

If you follow it exactly, those arguments are set from recently set variables. But yes - it does not hurt to pass them explicitly.

[potiuk]

especially - worth spelling out the --package-file which otherwise requires this package to be in cwd (so you have to do cd dev before

[vincbeck]

If you follow it exactly, those arguments are set from recently set variables. But yes - it does not hurt to pass them explicitly.

Interesting, I might have missed something then

[vincbeck]

especially - worth spelling out the --package-file which otherwise requires this package to be in cwd (so you have to do cd dev before

That's the thing, I was in dev directory and could not find the file. When provided --packages-file dev/packages.txt it worked (still inside dev directory)

[jscheffl]

Static checks are fixed in #58835, failure can be ignored.

[github-actions]

Backport successfully created: v3-1-test

Status	Branch	Result
✅	v3-1-test

[jscheffl]

Providers are released from main, no backport needed in my view.