Add "Quick Actions" flow after remote setup and to Overview/Remotes

[rorar]

Pre-submission checks

• I have searched both open and closed issues and confirmed this doesn't already exist
• I have checked the roadmap and this isn't already planned
• This feature aligns with the project's scope (RClone management)

Feature Description

Currently, new users are proposed with a dashboard with many options.
Underlying are the settings from every remote.
The settings are proposed "as is" but explanations are missing that guides the users to their goals.
example (high level) User Story:
User set up the remote and now wants to sync an Logseq/Obsidian vault, as there are many tutorials out there.

Currently the user needs basic understanding

• what's a mount
• what's sync is
• what bisync is
• about copy operations
  and how to tell them apart.

Proposed Solution

• A GUI "What's next?" modal after remote setup,
• also a Quick Actions Button on the dashboard that shares a kernel with "What's next?".

Users get guided to their goals.
For example:
Click on Quick Actions, get a predefined list of actions (like syncing a Obsidian/Logseq vault), and/or can simply choose their own without digging through all the settings.

Optionally and/or for the future:
using natural language with https://github.com/dip/cmdk (or similiar):
I want to ((connect)) ((Google Drive)) and ((sync)) files between "/home/rorar/Logseq" and ((Google Drive))

Does that makes sense to you? I know this is a really rough draft. If you want to, let's discuss this further! :)

Feature Category

UI/UX Improvement

Applicable Versions

• Desktop (GUI application with window)
• Headless (Web server accessed via browser)
• Portable (Standalone executable)
• All versions

Mockups/Screenshots

No response

Technical Considerations

No response

Additional Context

Also improves accessibility 💛

Would greatly get along with #232

[Hakanbaban53]

I Really like this idea, especially the natural-language bonus concept. The mount/sync/bisync/copy confusion is a real onboarding pain point, and guiding users by goal instead of raw settings makes a lot of sense.
Adding this to the long-term roadmap, other features are ahead in the queue, but this is planned for ~3-4 months out. Will revisit then, feel free to keep discussing/refining the idea in the meantime 🙂