feat: add test connection button to ui

[kevinhongzl]

closes: #50607

Why

The "test connection" fuctionality is currently missing in Airflow 3 UI.

What

Add a "Test Connection" button to each connection entry.

test-connection-button.mp4

---

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

[pierrejeambrun]

Nice, thanks for the pull request.

There is a configuration option core.test_connection to enable or not this feature. We should read that config and display or not the buttons depending on the value.

To retrieve this value in the front-end, you'll most probably need to add the value to the ui/config.py get_configs endpoint. This endpoint is called at the initialization of the web application and you can access the value through the useConfig hook.

[kevinhongzl]

@pierrejeambrun Thanks for the review! I've just updated this PR. We can now control the state of the button via airflow.cfg.

[pierrejeambrun]

Nice, a few suggestiosn / nit.

Looking good overall.

[pierrejeambrun]

Thanks, we can improve in follow up PRs if needed. (The toast message on success, not sure we need to display the msg there)

[pierrejeambrun]

Actually I think something is wrong with the toaster, see bellow, connection failed, but we show 200, that's confusing.

Toaster need fixing.

[pierrejeambrun]

Also, even on success that true false message doesn't bring much information.

[kevinhongzl]

Actually I think something is wrong with the toaster, see bellow, connection failed, but we show 200, that's confusing.
Also, even on success that true false message doesn't bring much information.

Yeah. It confused me as well, but that's how our api currently works.

The test connection API returns 200 with a boolean status, true for successfully creating a connection and false for connection error. However, there are also 401, 403, and 422 responses.... I can't figure out how this was designed from the docs, so I simply present information retrieved from the api with toasters.

https://airflow.apache.org/docs/apache-airflow/stable/stable-rest-api-ref.html#operation/test_connection

I need some hints or suggestions on how to deal with this.

[kevinhongzl]

Yeah. It confused me as well, but that's how our api currently works.

The test connection API returns 200 with a boolean status, true for successfully creating a connection and false for connection error. However, there are also 401, 403, and 422 responses.... I can't figure out how this was designed from the docs, so I simply present information retrieved from the api with toasters.

https://airflow.apache.org/docs/apache-airflow/stable/stable-rest-api-ref.html#operation/test_connection

I need some hints or suggestions on how to deal with this.

@pierrejeambrun Eventually I removed the toasts which can be misleading for now. I'd like to help if we have further discussions and follow-up issues!

[bbovenzi]

One last thing. Let's not add any new plaintext. Instead, add each one to the i18n/en/ directory at least.