Add team to list variables and list connections pages

[vincbeck]

Add team as column to list variable and list connection pages. I add it only if the multi-team mode is enabled.

Plus, I found out several bugs when I was testing edit variable and connection. I fix these bugs as part of this PR as well.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[pierrejeambrun]

Thanks for the PR.

We tend to never mutate objects because react diffing algorithm will compare references and not render the update if the object was mutated in place.

This is why you see a lot of:

const newArray = [...oldArray, ,newItem]

Here we are outside of a react component so it should be fine. (a new columns object is created on every render anyway)

[pierrejeambrun]

#61123 Small adjustment so people do not copy/past this by mistake. (even if it's fine in this current form it could easily bait someone working on a similar component)

[vincbeck]

Add team as column to list variable and list connection pages. I add it only if the multi-team mode is enabled.

Plus, I found out several bugs when I was testing edit variable and connection. I fix these bugs as part of this PR as well.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[pierrejeambrun]

Thanks for the PR.

We tend to never mutate objects because react diffing algorithm will compare references and not render the update if the object was mutated in place.

This is why you see a lot of:

const newArray = [...oldArray, ,newItem]

Here we are outside of a react component so it should be fine. (a new columns object is created on every render anyway)

[pierrejeambrun]

#61123 Small adjustment so people do not copy/past this by mistake. (even if it's fine in this current form it could easily bait someone working on a similar component)

[vincbeck]

Add team as column to list variable and list connection pages. I add it only if the multi-team mode is enabled.

Plus, I found out several bugs when I was testing edit variable and connection. I fix these bugs as part of this PR as well.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[pierrejeambrun]

Thanks for the PR.

We tend to never mutate objects because react diffing algorithm will compare references and not render the update if the object was mutated in place.

This is why you see a lot of:

const newArray = [...oldArray, ,newItem]

Here we are outside of a react component so it should be fine. (a new columns object is created on every render anyway)

[pierrejeambrun]

#61123 Small adjustment so people do not copy/past this by mistake. (even if it's fine in this current form it could easily bait someone working on a similar component)

[vincbeck]

Add team as column to list variable and list connection pages. I add it only if the multi-team mode is enabled.

Plus, I found out several bugs when I was testing edit variable and connection. I fix these bugs as part of this PR as well.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[pierrejeambrun]

Thanks for the PR.

We tend to never mutate objects because react diffing algorithm will compare references and not render the update if the object was mutated in place.

This is why you see a lot of:

const newArray = [...oldArray, ,newItem]

Here we are outside of a react component so it should be fine. (a new columns object is created on every render anyway)

[pierrejeambrun]

#61123 Small adjustment so people do not copy/past this by mistake. (even if it's fine in this current form it could easily bait someone working on a similar component)

[vincbeck]

Add team as column to list variable and list connection pages. I add it only if the multi-team mode is enabled.

Plus, I found out several bugs when I was testing edit variable and connection. I fix these bugs as part of this PR as well.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[pierrejeambrun]

Thanks for the PR.

We tend to never mutate objects because react diffing algorithm will compare references and not render the update if the object was mutated in place.

This is why you see a lot of:

const newArray = [...oldArray, ,newItem]

Here we are outside of a react component so it should be fine. (a new columns object is created on every render anyway)

[pierrejeambrun]

#61123 Small adjustment so people do not copy/past this by mistake. (even if it's fine in this current form it could easily bait someone working on a similar component)

[vincbeck]

Add team as column to list variable and list connection pages. I add it only if the multi-team mode is enabled.

Plus, I found out several bugs when I was testing edit variable and connection. I fix these bugs as part of this PR as well.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[pierrejeambrun]

Thanks for the PR.

We tend to never mutate objects because react diffing algorithm will compare references and not render the update if the object was mutated in place.

This is why you see a lot of:

const newArray = [...oldArray, ,newItem]

Here we are outside of a react component so it should be fine. (a new columns object is created on every render anyway)

[pierrejeambrun]

#61123 Small adjustment so people do not copy/past this by mistake. (even if it's fine in this current form it could easily bait someone working on a similar component)

[vincbeck]

Add team as column to list variable and list connection pages. I add it only if the multi-team mode is enabled.

Plus, I found out several bugs when I was testing edit variable and connection. I fix these bugs as part of this PR as well.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[pierrejeambrun]

Thanks for the PR.

We tend to never mutate objects because react diffing algorithm will compare references and not render the update if the object was mutated in place.

This is why you see a lot of:

const newArray = [...oldArray, ,newItem]

Here we are outside of a react component so it should be fine. (a new columns object is created on every render anyway)

[pierrejeambrun]

#61123 Small adjustment so people do not copy/past this by mistake. (even if it's fine in this current form it could easily bait someone working on a similar component)

[vincbeck]

Add team as column to list variable and list connection pages. I add it only if the multi-team mode is enabled.

Plus, I found out several bugs when I was testing edit variable and connection. I fix these bugs as part of this PR as well.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[pierrejeambrun]

Thanks for the PR.

We tend to never mutate objects because react diffing algorithm will compare references and not render the update if the object was mutated in place.

This is why you see a lot of:

const newArray = [...oldArray, ,newItem]

Here we are outside of a react component so it should be fine. (a new columns object is created on every render anyway)

[pierrejeambrun]

#61123 Small adjustment so people do not copy/past this by mistake. (even if it's fine in this current form it could easily bait someone working on a similar component)