Catch a couple other 404/401 issues for Bedrock Operators

[o-nikolas]

Similar to the KB creation retry logic here:

airflow/providers/amazon/src/airflow/providers/amazon/aws/operators/bedrock.py

Lines 463 to 504 in d8e591e

	def execute(self, context: Context) -> str:
	def _create_kb():
	# This API call will return the following if the index has not completed, but there is no apparent
	# way to check the state of the index beforehand, so retry on index failure if set to do so.
	# botocore.errorfactory.ValidationException: An error occurred (ValidationException)
	# when calling the CreateKnowledgeBase operation: The knowledge base storage configuration
	# provided is invalid... no such index [bedrock-sample-rag-index-abc108]
	try:
	return self.hook.conn.create_knowledge_base(
	name=self.name,
	roleArn=self.role_arn,
	knowledgeBaseConfiguration=self.knowledge_base_config,
	storageConfiguration=self.storage_config,
	**self.create_knowledge_base_kwargs,
	)["knowledgeBase"]["knowledgeBaseId"]
	except ClientError as error:
	error_message = error.response["Error"]["Message"].lower()
	is_known_retryable_message = (
	"no such index" in error_message
	# It may also be that permissions haven't even propagated yet to check for the index
	or "server returned 401" in error_message
	or "user does not have permissions" in error_message
	)
	if all(
	[
	error.response["Error"]["Code"] == "ValidationException",
	is_known_retryable_message,
	self.wait_for_indexing,
	self.indexing_error_max_attempts > 0,
	]
	):
	self.indexing_error_max_attempts -= 1
	self.log.warning(
	"Vector index not ready, retrying in %s seconds.", self.indexing_error_retry_delay
	)
	self.log.info("%s retries remaining.", self.indexing_error_max_attempts)
	sleep(self.indexing_error_retry_delay)
	return _create_kb()
	raise
	self.log.info("Creating Amazon Bedrock Knowledge Base %s", self.name)
	knowledge_base_id = _create_kb()

We need retries around starting the ingestion job because the index may not be ready or accessible.

I also added tests to cover the retry behaviour.

---

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