Fix package ID length adjustment logic in Get-BcNuGetPackageId function

[MoritzTSR]

The Get-BcNuGetPackageId function causes an issue when working with the DynamicsBCPublicFeeds for AppSource Symbols.

Although the maximum allowed length for a NuGet Package ID is 100 characters, the function currently truncates the ID to 99 characters. This leads to a mismatch with the actual package IDs published in the AppSourceSymbols feed, which use the full 100-character length.

Example

1. Original	TRASERSoftwareGmbH.TRASERECMConnect365xShareflexDocuments.symbols.c909c76e-7140-4e34-ba8e-7b47a8fe0247 (101 characters)
2. Output from Get-BcNuGetPackageId	TRASERSoftwareGmbH.TRASERECMConnect365xShareflexDocume.symbols.c909c76e-7140-4e34-ba8e-7b47a8fe0247 (99 characters)
3. Actual in AppSourceSymbols	TRASERSoftwareGmbH.TRASERECMConnect365xShareflexDocumen.symbols.c909c76e-7140-4e34-ba8e-7b47a8fe0247 (100 characters)

Impact

This one-character mismatch leads to failed package resolution with the Feed.

DynamicsBCPublicFeeds: https://dynamicssmb2.visualstudio.com/DynamicsBCPublicFeeds/_artifacts/feed/AppSourceSymbols

[mazhelez]

Can you also please add release notes

[MoritzTSR]

@microsoft-github-policy-service agree company="TRASER Software GmbH"

[mazhelez]

Hey @MoritzTSR

Thanks a lot for taking the time to contribute to BCContainerHelper!
After getting a closer look by the BCContainerHelper team, it looks like your change to Get-BcNuGetPackageId is breaking for the existing packages.
E.g. packages' names that are created via Get-BcNuGetPackageId might be trimmed down to 99 characters and, if we accept your change, these packages will not be found anymore.