Webpack config naming convention: ServerClientOrBoth.js uses PascalCase while siblings use camelCase

[ihabadham]

The webpack config directory has an inconsistent naming convention:

config/webpack/
├── ServerClientOrBoth.js    ← PascalCase
├── serverWebpackConfig.js   ← camelCase
├── clientWebpackConfig.js   ← camelCase
├── commonWebpackConfig.js   ← camelCase
├── development.js           ← lowercase
├── production.js            ← lowercase
└── test.js                  ← lowercase

In the Node.js/JS ecosystem, PascalCase files conventionally signal React components or classes, not utility/config modules. ServerClientOrBoth.js is a webpack config orchestrator — the same category as its camelCase siblings.

History: The name ServerClientOrBoth.js was established in the react_on_rails_demo_ssr_hmr repo in Jan 2022 (PR #29) and adopted in react_on_rails_pro/spec/dummy. PR #2284 aligns the base generator with this convention, replacing the previous generateWebpackConfigs.js.

Not urgent or blocking. Just flagging the inconsistency for future consideration. Renaming would require updating references in generator templates, gsub transform paths, test fixtures, and the demo app.

Found during PR #2284 code review.