Make strongly-unique hyphen-insensitive

[bvisness]

In #197 @lukewagner discussed making the strongly-unique algorithm also hyphen-insensitive. There was also some discussion of how strong this needed to be, but in my opinion it makes the most sense to remove hyphens entirely when checking for uniqueness, as this completely prevents names that differ only in case.

This is already a concern for us in Firefox, as an identifier like [method]a-b.AB on resource type a-b will produce a class named AB (PascalCase), and a method named AB (theoretically camelCase, but acronym). That's maybe workable for us as far as JS goes (because the constructor is just named constructor), but obviously other languages like Java and C# would choke on this case as well. I don't see a good reason for component interfaces to require case sensitivity.

[badeend]

I think this makes sense and offers wider compatibility across different languages 👍

[lukewagner]

Good point! Makes sense to me. It might be good to get a bit of implementation feedback (to see if this breaks anything) before merging though.

[bvisness]

Yeah, for sure. I do think this is a direction we want to go but there's no urgency to merge this; we can work around stuff for now (and are unlikely to encounter this in practice).