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

Start with the `rewire-pipeline` command and reproduce the issue against an ADO YAML pipeline without explicit trigger overrides. Compare the pipeline definition before and after the command, focusing on the `triggers` and `options` objects; done means the YAML triggers remain intact and the override checkbox is not enabled unexpectedly.

Written by the indexing model from the issue text.