Add file alias and link editing abilities to suggester-family elements

[jglev]

Background

• The Suggester, List Suggester, and Inline List Suggester elements that Meta Bind provides allow the use of an optionQuery argument to specify a Dataview query.
• Currently, the results returned from optionQuery only include a list of file names from a given folder, and ignores file aliases (which are set in files' aliases frontmatter field).
• Somewhat similarly, the Suggester, List Suggester, and Inline List Suggester elements do not allow changing the display text of links once one has been chosen.

What changed

• Made Suggester, List Suggester, and Inline List Suggester optionQuery results include aliases of files, alongside the current filename-based results.
• Gave Suggester, List Suggester, and Inline List Suggester a new icon or right-click menu item, allowing the user to edit the link text once an option has been selected.

---

How to see changes

1. Check out the branch and build the plugin for the example vault in the repo:

   git checkout suggester-aliases-and-editable-links
   bun run dev

2. Within the example vault:

   1. Go to Input Fields/Suggester.md. Note that the example suggester elements that use optionQuery now have a pen icon next to them. Try clicking on the pen icon and changing the link text.

      

   2. Try adding a value to the aliases frontmatter field for any note in the example vault. Then try adding a Suggester, List Suggester, or Inline List Suggester with optionQuery, and try searching for that alias:

      

Additional notes

I needed these changes for a workflow I use, and generated them largely through vibe-coding with GitHub CoPilot with various Claude models. While this changeset was interactively vibe-coded, I did manually inspect all of the changes and confirm that they look sensible to me. (If it's helpful to know, as well, I did manually write this PR description.) With that said, if it's a problem that these changes were generated using an automated code assistant, I'll understand.

I've squashed the changes into a single commit, figuring that that might make them easier to review as a whole.