As far as I've been able to determine, Edge will follow the same timeline as Chrome since Edge is based on Chromium. The timeline is published here:
The Privacy Sandbox Timeline for the Web
https://privacysandbox.com/open-web/#the-privacy-sandbox-timelineAs far as a deprecation trial, see here:
Preserving critical user experiences
https://developers.google.com/privacy-sandbox/3pcd/temporary-exceptions/preserving-critical-user-exp...See also:
Google
Third-party cookies restricted by default for 1% of Chrome users
https://developers.google.com/privacy-sandbox/blog/cookie-countdown-2024janPrepare for phasing out third-party cookies
https://developers.google.com/privacy-sandbox/3pcdCookies Having Independent Partitioned State (CHIPS)
https://developers.google.com/privacy-sandbox/3pcd/chipsNote: If you are a developer using either .NET (formerly .NET Core) or .NET Framework, as of this time, neither will support the new "Partitioned" cookie attribute as was done for the "SameSite" attribute. The solution Microsoft proposed to us was to use the CookieOptions.Extensions property in .NET or an outbound URL Rewrite rule in .NET Framework.
Thanks
Mike