Feat(Chromium-Bookmarks): Added caching, Flatpak support, Favicons and performance/UX improvements

[JdotCarver]

Note:

• This PR addresses issue [chromium-bookmarks] Flatpak Support #250
• This PR was co-authored by AI (Claude Opus 4.7, Deepseek V4-pro-thinking)
• This PR was done on Vicinae v0.20.13. #1334 addresses the ordering issues found in the screenshot.
• The images provided in this PR are for demonstrational purposes only. I am not endorsing any sites found in the random bookmarks I have collected over the years.

What Changed

Browser Support

• Added support for Chromium Flatpaks.
• Added smarter logic that follows browser symlink to know if the browser is actually a symlinked flatpak.
• Added support to show Browser profile in Bookmark details.

Improved Logic

• Added caching, for faster results loading.
• Tightened up the matching to have more relevant results.
• Added an (optional) render load limit, for faster results rendering.

Quality of Life Improvements

• Added (optional) favicon support, for better bookmark differentiation.
• Added the option to show full URLs instead of domains.
• Tweaked the icon for Favourited bookmarks, they are now Stars instead of the same bookmark icon but tinted.
  • And added handling for Favourites with Favicons.
  • Removed the tint in the action menu to be more in line with the rest of the UI.
• Title cased the Action Names
• Added Keyboard Shortcuts to Favourite a Bookmark, Quicklink a Bookmark and Open Extension Settings

I tried to test each feature extensively but if I have missed anything please notify me and I'll fix it.

Comparison

Search Results

Original

Improved

More pertinent search results.

‎ ‎ ‎ ‎

Menu Items

Original

Improved

Interface is more unified. All actions have shortcuts.
You can directly jump into the settings to easily tweak.
Creating shortcuts is super convenient, everything pre-fills for you.

Preferences

Safe defaults built-in.
Any users from the previous version only has under the under-the-hood improvements and can opt-into the new features.
The Vicnae UI can only display a list of 10 elements, so the render limit only serves as an invisible way to boost speed for users, with further improvements at higher numbers. I personally have it set at 30, so I deemed the default of 100 to be more than reasonable.

[JdotCarver]

For some reason the postprocessing workflow is failing after modifying these unrelated files:

• extensions/iconify/package-lock.json
• extensions/pass/package-lock.json

My PR only changes extensions/chromium-bookmarks and does not touch those.
The workflow then tries to auto-commit "Fix package-lock.json" back to my fork, but the push fails with a 'remote: Permission denied to github-actions[bot]'

I have not touched those extensions. Should I do anything, or is the postprocessing workflow incompatible with fork PRs here?