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

`rewire-pipeline` コマンドから始め、明示的なトリガーのオーバーライドがない ADO YAML パイプラインで問題を再現します。コマンド実行前後のパイプライン定義を比較し、`triggers` オブジェクトと `options` オブジェクトに注目します。YAML のトリガーがそのまま維持され、オーバーライドのチェックボックスが予期せず有効にならなければ完了です。

索引モデルが issue の本文から書いたものです。