fix(macOS Button): Use Fluent 2 alias tokens

[Saadnajmi]

Platforms Impacted

• iOS
• macOS
• win32 (Office)
• windows
• android

Description of changes

The macOS Button color tokens were still being set by older, deprecated tokens instead of the Fluent-2-vetted alias tokens. Let's update them.

Notable changes and things I learned (though I probably missed a few):

• macOS default buttons use neutralBackground2 / neutralForeground2 / neutralstroke2 for a softer overall color set
• macOS in general shouldn't have a hover state for its' buttons, except Subtle Button. Some alias tokens don't respect this, see the followup tasks.
• Apart from Subtle Button, I try to always define a non-transparent border, which adds 2 px to the overall width and height of each button. Subtle Button has bugs, see the followup tasks.
• strokeFocus1 and strokeFocus2 seem very win32 specific, so we probably shouldn't use them elsewhere. They seem explicitly for the two-toned focus border.

Followups:

• A PR to delete the old `default / ghost / etc ramp
• [macOS Alias Tokens] brandBackgroundHover doesn't match brandBackground on macOS #3780
• [macOS Alias Tokens] Subtle Button in HC should keep it's border on hover and pressed states #3781
• [macOS Alias Tokens] brand tokens are using Fluent 1 color ramp #3782

Verification

Video of how the buttons look now.

Screen.Recording.2024-10-16.at.3.44.39.PM.mov

Pull request checklist

This PR has considered (when applicable):

• Automated Tests
• Documentation and examples
• Keyboard Accessibility
• Voiceover
• Internationalization and Right-to-left Layouts

[rurikoaraki]

"and that our jest tests are actually testing that on macOS."

-- I think right now our jest tests only run on one platform at a time, so we kinda have to pick which platform we want tested.

[Saadnajmi]

Moving back to draft, as I am making updates to the token definitions

[Saadnajmi]

Token definition updates blocked upstream. Merging as is.