Destroying AnimationOutput writes to the animator default values, breaking certain workflows

Steps to reproduce:

1. Open the attached project: "AnimationOutput_Repro"
2. 2. Open "DefaultValues-TestScene.unity" Scene
3. Enter Play mode
4. Note the Continuous motion of the object and its location
5. Enable the "Custom Graph" object
6. Let the new animation play a couple of loops
7. Disable the "Custom Graph" object

Expected results: Continuous motion returns, as if the custom object was never enabled
Actual results: Depending on the error introduced, which depends on when in the loop the object was disabled, the motion is now skipping and non-continuous. Different to the state before the object was enabled

Explanation:

The "Custom Graph" object creates a playable graph during OnEnable and destroys is during OnDisable. The playable graph contains a animation output that plays an animation clip using the animator in the scene. 

When the object is disabled, its graph is destroyed and the animation output is also destroyed. The destroy operation changes the animator's default values.

How to reproduce with Timeline:

Steps to reproduce:
1. Open the attached user's project "Animator-DefaultValue-Issues.zip"
2. Open "DefaultValues-TestScene.unity" Scene
3. Enter Play Mode
4. Note the Continuous motion of the object, no skipping or jumping
5. Enable the "Timeline" GameObject
6. Let the new animation play a couple of loops
7. Disable the "Timeline" GameObject

Expected results: Continuous motion returns, as if the Timeline was never enabled
Actual results: Depending on the error introduced, which depends on when in the loop the Timeline was disabled, the motion is now skipping and non-continuous. Different to the state before the Timeline was enabled

Reproducible with: 2021.3.32f1, 2022.3.14f1, 2023.2.1f1, 2023.3.0a15

Testing environment: Windows 10
Not reproducible on: No other environment tested

Notes:
-When a Timeline is toggled on and then off for an animtor, the animator's default values are affected. If an animation was relying on expected default values then that animation will no longer work as expected.
-A key part of the workflow is the use of "Write Default Values On Disable" on the animator and "Write Default Values" in each Animator State
-The customer is well aware of how "Write Default Values On Disable" and "Keep Animator State on Disable" work. They wish to use only "Write Default Values On Disable : true" as this functionality generates the simplest workflow for them when they're driving and pooling animators
-Videos attached explaining the issue in more detail "DefaultValue_Explainer.mp4" and "DefaultValue_Addition.mp4"