Write test to make sure asset naming matches component

[jonrohan]

Description

This PR introduces a test to make sure that assets are named to match the component ruby file. This follows convention setup for view components and also allows us to write tests around this convention to match assest with their component.

app/components
  ├── component.rb
  ├── component.pcss
  └── component.html.erb

Integration

Does this change require any updates to code in production?

no

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews

[changeset-bot]

🦋 Changeset detected

Latest commit: 303617a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@primer/view-components	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[camertron]

Hmm I'm not sure I'm in favor of this change. I learned recently that web components are required to include a hyphen in their names, eg. nav-list instead of navlist. Up until now it hasn't been a problem, but I was bitten last week by banner and flash. Apparently it's common to prefix single-word web component names with x-, so the custom element names are x-banner and x-flash. We have an eslint rule that forces the element name to match the file name, so I had to use x_banner.ts. I really don't want to have to name the component x_banner.rb and x_banner.html.erb too 😓

[jonrohan]

Hmm I'm not sure I'm in favor of this change. I learned recently that web components are required to include a hyphen in their names, eg. nav-list instead of navlist. Up until now it hasn't been a problem, but I was bitten last week by banner and flash. Apparently it's common to prefix single-word web component names with x-, so the custom element names are x-banner and x-flash. We have an eslint rule that forces the element name to match the file name, so I had to use x_banner.ts. I really don't want to have to name the component x_banner.rb and x_banner.html.erb too 😓

I can drop the ts file requirement. I do need the CSS files to match so I can build testing around class coverage

[camertron]

Ok I'm cool with that. We might also consider relaxing the eslint rule.