Fix invalid escape sequence in EKS Hook module

[Taragolis]

Body

Right now import airflow/providers/amazon/aws/hooks/eks.py raise DeprecationWarning / SyntaxWarning (depends on python version)

{
  "category":"DeprecationWarning",
  "message":"invalid escape sequence \\s",
  "filename":"airflow/providers/amazon/aws/hooks/eks.py",
  "lineno":79,
  "when":"collect",
  "node_id":null
}

We should avoid to use something that deprecated in Python itself years ago in Python 3.6.

airflow/airflow/providers/amazon/aws/hooks/eks.py

Lines 80 to 81 in b7ac00d

	output=$({python_executable} -m airflow.providers.amazon.aws.utils.eks_get_token \
	--cluster-name {eks_cluster_name} {args} 2>&1)

airflow/airflow/providers/amazon/aws/hooks/eks.py

Lines 91 to 93 in b7ac00d

	json_string=$(printf '{{"kind": "ExecCredential","apiVersion": \
	"client.authentication.k8s.io/v1alpha1","spec": {{}},"status": \
	{{"expirationTimestamp": "%s","token": "%s"}}}}' "$expiration_timestamp" "$token")

\ in the end of the line make sense only in regular strings, not in triple quoted, however right now it work as intended - remove new line in the end of the line

Note

This rule right now ignored in statical code checks (provided by ruff rule W605) on module level

airflow/pyproject.toml

Lines 392 to 393 in 79b5443

	# https://github.com/apache/airflow/issues/39252
	"airflow/providers/amazon/aws/hooks/eks.py" = ["W605"]

So it also required to remove this lines from pyproject.toml,

Warning

Ruff Autofix suggest use raw string here, however it is not a case here and better rewrite built this command.
Previous attempt #38734 is reverted #38864

Committer

• I acknowledge that I am a maintainer/committer of the Apache Airflow project.

[SoulPancake]

Is there more work left in this that I can help with? @Taragolis

[Taragolis]

There is only one things remaining, that it exact the thing which describe into the issue

This warning which might annoying end users because since Python 3.12+ such warnings become SyntaxWarning, see: python/cpython#98401, which are not ignored by default as DeprecatedWarnings

So if you would like to fix, feel free to make a PR