[template/nextjs] Fix personalize and feaas module not found error

[addy-pathania]

• This PR follows the Contribution Guide
• Changelog updated

Description / Motivation

For some unknown reason, the dependencies @sitecore-feaas/clientside and @sitecore-cloudsdk/personalize, which are listed as peerDependencies in @sitecore-jss/sitecore-jss-nextjs, are not being installed for some users. This is a workaround for this issue.

Testing Details

• Unit Test Added
• Manual Test/Other (Please elaborate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

[thezaff]

I've been using --force flag to install dependencies without this issue for a week now :)

[yavorsk]

In this case do we need the reference to @sitecore-feaas/clientside in the xmcloud add on?

[illiakovalenko]

@sc-addypathania Did you explore any other options? Is this problem related to Node.js version? And may be we can execute "npm install" with additional flags to workaround that?
Shortly, we shouldn't include any dependencies in a base template that are not used there

[addy-pathania]

So this issue is being caused by the legacy-peer-deps flag being set to true in one of the .npmrc files.
After setting it to false all the peer dependencies are installed fine.
Will add a bit more details to the open issue here
Closing this now.