[sitecore-jss-manifest][Nextjs] Allow component manifest definitions to define a template name

[ambrauer]

Description / Motivation

When deploying manifest items to Sitecore (via jss deploy), the resulting component and datasource template use the same name (implicit dependency between them). This update adds an optional templateName which can be used for component definitions, breaking that dependency. This value will be used when creating the datasource template item in Sitecore (instead of the component name).

This allows us to prefix templates only (separately from components).

Also included:

• Updates to the Next.js sample app with this new feature in mind (revert component names)
• Removed filename processing from jss create prefix logic (since component files are no longer prefixed)

Testing Details

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)
• Documentation update (non-breaking change; modified files are limited to the /docs directory)

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/sitecore-jss/edge-e2e-styleguide/ACwjjHTMqfXCctmVud8NPqm4ivAj
✅ Preview: Failed

[CobyPear]

Looks like there was some extra work to do inside of generateItems etc, but why did it seem to work yesterday?
Looks good other than that question.

[ambrauer]

@CobyPear We only made it through the renderings, I ran into additional errors when it got to the shared content examples.