MudAppBar: Fix default value of WrapContent (#6808, #6869)

[henon]

This is a hotfix of an accidental breaking change made by the PR #6808, which was remedied for MudToolbar with #6869 but for MudAppBar the wrong (breaking) default value was chosen, which is remedied in this PR.

[henon]

Any idea what's up with the MudExpansionPanel_Without_MultiExpansion_Doesnt_Crash_With_Multiple_Expanded_Tabs test?

[ScarletKuro]

Any idea what's up with the MudExpansionPanel_Without_MultiExpansion_Doesnt_Crash_With_Multiple_Expanded_Tabs test?

Yes, there is some inconsistency in this test.
However, I usually resolve this issue by re-triggering the tests, which typically leads to successful outcome.
Sometimes, for unknown reason the output exceeds the maximum limit of 100 lines in FluentAssertions, resulting in the following message:

Output has exceeded the maximum of 100 lines. Increase FormattingOptions.MaxLines on AssertionScope or AssertionOptions to include more lines.

I had similar inconsistencies arising from object nesting, I fixed it with the following code:

[OneTimeSetUp]
public void Init()
{
    AssertionOptions.FormattingOptions.MaxDepth = 100;
}

[OneTimeTearDown]
public void Cleanup()
{
    AssertionOptions.FormattingOptions.MaxDepth = 5; //default
}

I guess you can do similar fix with AssertionOptions.FormattingOptions.MaxLines.