Fix providers validation in check_files.py after switch to the hatch builds

[Taragolis]

related: #36902

Just figure out that naming also affected to providers packages

❯ breeze release-management prepare-provider-packages microsoft.azure google amazon --version-suffix-for-pypi dev0 --package-format both
Good version of Docker: 24.0.7.
Good version of docker-compose: 2.23.3
...

Successfully built packages!


Packages available in dist:

apache_airflow_providers_amazon-8.16.0.dev0-py3-none-any.whl
apache_airflow_providers_amazon-8.16.0.dev0.tar.gz
apache_airflow_providers_google-10.13.1.dev0-py3-none-any.whl
apache_airflow_providers_google-10.13.1.dev0.tar.gz
apache_airflow_providers_microsoft_azure-8.5.1.dev0-py3-none-any.whl
apache_airflow_providers_microsoft_azure-8.5.1.dev0.tar.gz

I think that it not required to change check_upgrade_check and maybe even better to remove this option from the file

airflow/dev/check_files.py

Lines 146 to 157 in 98fb11b

	def check_upgrade_check(files: list[str], version: str):
	print(f"Checking upgrade_check for version {version}:\n")
	version = strip_rc_suffix(version)
	expected_files = expand_name_variations(
	[
	f"apache-airflow-upgrade-check-{version}-bin.tar.gz",
	f"apache-airflow-upgrade-check-{version}-source.tar.gz",
	f"apache_airflow_upgrade_check-{version}-py2.py3-none-any.whl",
	]
	)
	return check_all_files(expected_files=expected_files, actual_files=files)

---

^ 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 newsfragments.