Handle both forms of charmId access

[bfollington]

This is a strange bug, it might imply mixing up the result and source cell somewhere? Or [ID] missing in some objects?

---

Summary by cubic

Fixes backlink creation and charm lookup in the code editor. Enter now creates a new backlink reliably, and charm matching handles both ID forms.

• Bug Fixes
  • Match charms by checking IDs from both mentionableArray.get()[i] and mentionableArray.key(i].
  • When no backlink matches: use pattern-based creation if available; otherwise emit backlink-create.
  • Apply the same pattern-aware creation to the “Create new backlink” action.

[seefeldb]

This might overmatch.

The other concerning part is that if these mentionables are all runnable charm, then they must be result cells and so always their own docs. The case where [ i ] isn't a link, but an inline object (what you get when not setting [ID] on a .set) would mean we copied the results away from the runnable stuff, possibly.

Oh, or is mentionables an object that boxes the charm reference? If so, just compare the actual charm reference!

[seefeldb]

I have to double check, but I think that getEntityId ignores to path part, so all of these IDs will be the same irrespective of i.