Can't mark old package as deprecated when renaming

Hello! In order to solve https://github.com/Maxim-Mazurok/google-api-typings-generator/issues/652 in https://github.com/Maxim-Mazurok/google-api-typings-generator/pull/655 I'll be changing the naming pattern of @types/gapi.client.* packages in order to accommodate multiple versions that can't be described as ${major}.${minor}, such as v2beta1, directory_v1, reports_v1, etc.

So now instead of having one @types/gapi.client.admin package, we'll have two: @types/gapi.client.admin-directory_v1 and @types/gapi.client.admin-reports_v1.

The current @types/gapi.client.admin package is essentially the same as the new @types/gapi.client.admin-reports_v1 will be.

So, I'd like to mark @types/gapi.client.admin as deprecated and point developers to the new one.

I could only find one way to mark @types package as deprecated on npm: using notNeededPackages.json. But this will say Bla provides its own type definitions which isn't correct, we're just renaming the types package.

I'd like to have an option to deprecate the old name in favor of the new one so that devs know where to find new versions.

I'd be happy to open PR to add renamedPackages.json with the option to specify the old and the new name that would work similarly to generateNotNeededPackage(), let me know if this is something you'd be open to, thanks!

For now, I'll probably add some deprecation messages and will keep both new and old packages.

Start by reviewing notNeededPackages.json and the generateNotNeededPackage() path mentioned in the issue. Determine how a renamed package could be deprecated while pointing developers to its replacement, then verify that the generated npm metadata gives the intended guidance for both package names.