Microsoft Teams (work or school) "New" and Microsoft Teams Classic appear to have same ID when using update

Brief description of your issue

Microsoft Teams "New" and Microsoft Teams Classic appear to have same ID when using update. There are others bugs with similar issues but with Teams site wide installer and not Classic and the "new" work and school version. Both classic and "new" Microsoft Teams are installed on the system. Winget produces the following when running winget update which indicates Teams classic and new Teams appear to have the same ID.

The following packages have an upgrade available, but require explicit targeting for upgrade:
Name                    Id              Version     Available            Source
-------------------------------------------------------------------------------
Microsoft Teams classic Microsoft.Teams 1.7.00.6058 24074.2321.2810.3500 winget

winget list --id teams
Name                             Id                   Version              Available            Source
------------------------------------------------------------------------------------------------------
Microsoft Teams classic          Microsoft.Teams      1.7.00.6058          24074.2321.2810.3500 winget
Microsoft Teams                  Microsoft.Teams.Free 24060.3102.2733.5911                      winget
Microsoft Teams (work or school) Microsoft.Teams      24074.2321.2810.3500                      winget

Steps to reproduce

Winget update is run.

Expected behavior

Winget to update Microsoft Teams Classic

Actual behavior

Winget is attempting to update Microsoft Teams Classic to "new" Microsoft Teams but that is already installed on system.

Environment

Windows Package Manager v1.7.10861
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22631.3447
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.10861.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

Start by reproducing the issue with winget update and winget list --id teams on the stated Windows Package Manager version. Compare the identifiers and installed versions for Microsoft Teams classic and Microsoft Teams (work or school); done means the two products are handled as distinct packages during update without targeting one as the other.