fix(load-styles): export css module classes as-is

[zacowan]

Description

Note: this reverts an unintentional breaking change introduced with v7 of the one app bundler.

Updates load-styles to map css module class names using an "as-is" strategy, rather than a "camelCaseOnly" strategy in order to match the behavior of the webpack-based styles loader in @americanexpress/one-app-bundler@6. To be fully backwards-compatible with the webpack implementation, the exports needed to be changed to cjs-style exports.

Motivation

In switching over to load-styles provided by the dev bundler with the release of @americanexpress/one-app-bundler@7, an unintentional breaking change was introduced to the way that css module classes were mapped and exported when loading the styles. The webpack-based styles loader exported classes "as-is", while the esbuild-based styles loader exported classes in "camelCaseOnly". Additionally, the webpack delivered exports using cjs-style exports, rather than esm-style exports.

Test Conditions

Added unit tests for the most common ways people would define classes in css modules. Additionally, validated the changes in a test module.

Behavior in Production Bundler v6

Existing Behavior in Production (and dev) Bundler v7

New Behavior With This Change

Types of changes

Check boxes that apply:

• 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 not work as expected)
• Documentation (adding or updating documentation)
• Dependency update
• Security update

Checklist

Check boxes that apply:

• My code follows the code style of this project.
• My change requires a change to the documentation and I have updated the documentation accordingly.
• These changes should be applied to a maintenance branch.
• I have added the Apache 2.0 license header to any new files created.

[code-forger]

This will need backporting too please