`rewire-pipeline` Command Switches YAML Triggers

## Description
After running the `rewire-pipeline` against an ADO YAML pipeline, the pipeline options/triggers have been changed unexpectedly. Curling the definition content it looks like the `rewire-pipeline` command removes the pipeline definition `triggers` object and instead populates it with `options` (mine didn't have options before anyway). After manually unchecking the `Override the YAML continuous integration trigger from here` checkbox and curling the definition, the `triggers` object is repopulated.


**After Running Command**:

**After Manually Reverting/Unchecking**:

## Reproduction Steps
Run the `rewire-pipeline` command against an ADO YAML pipeline without any explicit pipeline definition trigger overrides. After running the command, edit the pipeline in ADO and navigate to the triggers. Notice the `Override the YAML continuous integration trigger from here` checkbox is checked.

Commencez par la commande `rewire-pipeline` et reproduisez le problème sur un pipeline YAML ADO sans remplacements explicites des triggers. Comparez la définition du pipeline avant et après la commande, en vous concentrant sur les objets `triggers` et `options` ; c’est terminé lorsque les triggers YAML restent intacts et que la case à cocher de remplacement n’est pas activée de manière inattendue.

Rédigé par le modèle d'indexation à partir du texte de l'issue.