Consider impact of glint on API design

Before glint/gts, having a modifier and helper with the same name didn't cause any issues, but it is a point of annoyance when working with glint. It's not a show stopper, because .gts file authors can easily alias the helper or modifier when importing it, but it would be good to consider a plan to evolve the addon to be more friendly in its default naming.

Start by reading the addon’s public API around helpers and modifiers with shared names, then look at how .gts authors using glint would import them. Done would require an agreed naming or migration plan for making the default API friendlier, but the issue does not name files, tests, or a specific change.

由索引模型根据 Issue 内容生成。