Enable unicorn/filename-case ESLint rule

[codykaup]

Simply enables our unicorn/filename-case ESLint rule and fixes any errors that appear.

📦 Published PR as canary version: 11.11.1--canary.1062.11128106915.0

✨ Test out this PR locally via:

npm install chromatic@11.11.1--canary.1062.11128106915.0
# or 
yarn add chromatic@11.11.1--canary.1062.11128106915.0

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00% (target: -1.00%)	❌ 66.67% (target: 80.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (c97b1b9)	8399	4513	53.73%
Head commit (e0cc85f)	8399 (+0)	4513 (+0)	53.73% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#1062)	15	10	66.67%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

[github-actions]

📦 Package Size: 4160 KB
✅ Compared to main: 0 KB c97b1b9 (4160 KB)

[jmhobbs]

I'm a little on the fence about the subcommand files. There is something nice about the symmetry of trim-stats-file being found in trim-stats-file.ts instead of trimStatsFile.ts

[codykaup]

I'm a little on the fence about the subcommand files. There is something nice about the symmetry of trim-stats-file being found in trim-stats-file.ts instead of trimStatsFile.ts

@jmhobbs So here's a funny thing... I'm actually the opposite 😅. To me, the filenames should all match and my brain translates the command name into the camel case for the filename when I go to search for it.

[jmhobbs]

@jmhobbs So here's a funny thing... I'm actually the opposite 😅. To me, the filenames should all match and my brain translates the command name into the camel case for the filename when I go to search for it.

Fair enough! Probably better to stick to the convention we have everywhere instead of making exceptions.