Renaming Favorites

[AlexKempen]

We should add the ability to rename favorites.

I think the logical place to start is renaming in-line, so a context menu option that makes the favorite title editable. I think for routes you can probably delete the current set-default-configuration endpoint and instead add the defaultConfiguration and name as optional parameters to the endpoint, similar to what we do for user settings today.

That also makes it possible for new favorites (from the insert menu) to have the current configuration automatically set as their default configuration, which I think is a nice bonus.

Also, don't forget to hide the rename favorite option in the insert menu (which will become an option once #10 is implemented.)

In the future I could also see being able to rename a favorite in the insert (and/or set-default-configuration menu, which should probably just get moved into the regular insert menu), but one caveat there is we probably need to first update to start drawing the distinction between inserting a favorite and inserting a part that you've favorited (since renaming makes sense in the former case but not the latter, and the distinction becomes relevant once we add the ability to favorite the same part multiple times).

[AlexKempen]

One additional thing we'll have to do with this is break Favorite searching out into it's own explicit Search instance since we now need to be able to build and search favorites completely independently from the main library (since custom names mean we can no longer rely on the library search being separate from the favorites search).

The existing search implementation is designed to run in the db (since we build the library search index at search time), so you'll probably need to extract some of the common search logic and possibly make some modifications since Favorite searching doesn't need as much metadata. For example, you probably don't need the group name since Favorites aren't in groups.

The favorites index can probably be built lazily at search time directly inside FavoritesList - perhaps factor out a favorite search result list componentwhen there's a search query (so we only build the search db when the user actually tries to search) and swap out the doSearch implementation (or perhaps just the searchDb you pass in, which also allows you to remove the favorite logic in doSearch).