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

Inizia con il comando `rewire-pipeline` e riproduci il problema su una pipeline YAML ADO senza override espliciti dei trigger. Confronta la definizione della pipeline prima e dopo il comando, concentrandoti sugli oggetti `triggers` e `options`; il lavoro è completato quando i trigger YAML rimangono intatti e la casella di override non viene abilitata inaspettatamente.

Scritto dal modello di indicizzazione a partire dal testo della issue.