Repair different run_id for OpenLineage START and FAIL events.

[kacpermuda]

There is an issue with OpenLineage FAIL event having different run_id than START event. This fixes the issue and add tests to prevent it from happening in the future.

The issue was that we decreased try_number in on_task_instance_failed as we wanted it to be the same as in on_task_instance_running (try_number is used to generate deterministic run_id). As it turned out, when on_task_instance_failed is called, the try_number is not yet automatically increased by Airflow, so we do not have to do that - it just need to be done in on_task_instance_success.

If You want to reproduce the issue run the below dag with OpenLineage integration, You should receive different run_id in START and FAIL event.

from airflow import DAG
from airflow.operators.bash import BashOperator
from datetime import datetime

with DAG(
    dag_id='test',
    start_date=datetime(2023, 11, 30),
    schedule_interval=None
) as dag:
    task = BashOperator(
        task_id='run_bash',
        bash_command='exit 1;'
    )

---

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