Reverts "Reland: Framework wide color (#54415) (#54737)"

[auto-submit]

Reverts: #54737

Initiated by: chingjun

Reason for reverting: Breaking internal tests. See b/363125155

Original PR Author: gaaclarke

Reviewed By: {matanlurey, jonahwilliams}

This change reverts the following previous change:
This PR was reverted because it requires a manual roll into the framework.

issue: flutter/flutter#127855
integration test: #54415

This does the preliminary work for implementing wide gamut colors in the Flutter framework. Here are the following changes: 1) colors now specify a colorspace with which they are to be interpreted 1) colors now store their components as floats to accommodate bit depths more than 8

The storage of this Color class is weird with float/int storage but that is a temporary solution to support a smooth transition. Here is the plan for landing this:

1. Land this PR
2. Wait for it to roll into the Framework
3. Land Switched CupertinoDynamicColor to implements Color flutter#153938 which will make CupertinoDynamicColor implement Color
4. Land another engine PR that rips out the int storage: Removes the int storage from Color #54714

Here are follow up PRs:

1. Changes DlColor to support wide gamut colors #54473 - changes DlColor so the wide gamut colors are rendered
2. Hooks up framework wide gamut to engine wide gamut #54567 - Hooks up these changes to take advantage of wide DlColor
3. Adds wide gamut framework test flutter#153319 - the integration test for the framework repo

There are some things that have been left as follow up PRs since they are technically breaking:

1. The math on lerp hasn't been updated to take advantage of the higher bit depth
2. operator== hasn't been updated to take advantage of the higher bit depth
3. hashCode hasn't been updated to take advantage of the higher bit depth
4. alphaBlend hasn't been updated to take advantage of the higher bit depth
5. toString hasn't been updated to take advantage of the higher bit depth

Pre-launch Checklist

• I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
• I read the [Tree Hygiene] wiki page, which explains my responsibilities.
• I read and followed the [Flutter Style Guide] and the [C++, Objective-C, Java style guides].
• I listed at least one issue that this PR fixes in the description above.
• I added new tests to check the change I am making or feature I am adding, or the PR is [test-exempt]. See [testing the engine] for instructions on writing and running engine tests.
• I updated/added relevant documentation (doc comments with ///).
• I signed the [CLA].
• All existing and new tests are passing.