Change NPM Package Name to cdk-nextjs?

[bestickley]

I think the "standalone" portion of the package name is a bit confusing and draws unnecessary attention to how open-next works (building nextjs in standalone mode). I think this construct should be the go-to package for anyone using CDK and Next.js hence the new suggested name: cdk-nextjs. This change would be timed well as we're soon to release stable v4. We could deprecate old package and print message saying to switch to cdk-nextjs package name.
CC: @kevin-mitchell, @onhate, @sonnydg, @manzinger, @AlbertSabate, @ApocDev, @okarlsson, @danethurber, @jadenv

[jaismith]

Agreed, these are deployment constructs and are not necessarily specific to the current build configurations supported by NextJs. It is not guaranteed that the "standalone" option will exist in future releases that these constructs support.

[kevin-mitchell]

To be honest I assumed the stand-alone bit was because of some sort naming collision or similar.