bug/issue 1223 handle incorrect nested SSR page bundle output name mapping

[thescientist13]

Related Issue

resolves #1223

Summary of Changes

1. Map SSR page output paths and bundle names to Rollup bundle names
2. Added relativeWorkspacePagePath as convenience to the graph for each page, should track as part of Content as Data #1167
3. Incorporated this change to handle a change in behavior in latest Node 18.20.x

Will make to align with work being done in #1212

TODO

1. fix windows build failures
2. Phantom .greenwood/_ directory?
3. Downstream testing
   • AnalogStudiosRI/www.blissri.com@f0f0fe4
   • https://66356e162788c46b161f40ab--thriving-kataifi-2b287f.netlify.app/photos/blissfest-2023/
4. Create an enhancement issue for making sure we have better control over output map naming - improve naming for (nested) bundled SSR page and API route entry points to better reflect original file based routing name #1226

---

Main issue was with very loose enforcement of output naming, such that when running this sort of pages through Rollup

src/
  pages/
    blog/
      index.js
    index.js

Both of those will come out of the same name to Rollup, and because they will be duplicates, you'll be getting unexpected names, like

• _index.js
• _index2.js
• _index3.js
• ...

So the main fix here is to map our bundle names to whatever Rollup spits out for now just keep things working and in sync.