Reassess component resolution strategy

[colinhicks]

From @gardnervickers in slack:

The only reason I bring up the question about keyword/symbol component identifiers is because the tutorial layout looks so much like hiccup syntax already. I can appreciate the desire for symmetry there though. I don’t think its terribly important either way as long as the backing components are not tied to resolving keyword->component.
I could see people wanting to use these components in devcards or their own projects, it would be nice if we could decouple our component resolution strategy from the component itself.