refresh connection if an exception is caught in "AzureDataFactory"

[Lee-W]

What's the issue?

When waiting for a long-running data factory pipeline run, it's possible that the Azure connection is expired and will need to be refreshed. This happens in (AzureDataFactoryPipelineRunStatusSensor(..., deferrable=True), and AzureDataFactoryRunPipelineOperator which will need changes in the following code sections.

AzureDataFactoryPipelineRunStatusSensor(..., deferrable=True)

airflow/airflow/providers/microsoft/azure/triggers/data_factory.py

Lines 73 to 77 in 1f22db7

	pipeline_status = await hook.get_adf_pipeline_run_status(
	run_id=self.run_id,
	resource_group_name=self.resource_group_name,
	factory_name=self.factory_name,
	)

AzureDataFactoryRunPipelineOperator(..., deferrable=True)

airflow/airflow/providers/microsoft/azure/triggers/data_factory.py

Lines 145 to 149 in 1f22db7

	pipeline_status = await hook.get_adf_pipeline_run_status(
	run_id=self.run_id,
	resource_group_name=self.resource_group_name,
	factory_name=self.factory_name,
	)

AzureDataFactoryRunPipelineOperator(..., deferrable=False)

airflow/airflow/providers/microsoft/azure/hooks/data_factory.py

Line 831 in 1f22db7

pipeline_run_status = self.get_pipeline_run_status(**pipeline_run_info)

What's changed?

Re-establish connection if an exception is caught in these sections, and set executed_after_refresh_token to False. If the exception does not relate to connection refresh, then the next round of status checking will still raise an exception and won't refresh the toekn

---

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