Expand rule automation and migration support

[alvst]

Summary

• Added Forel rule import/export, including native .forelrules exports and compatible Hazel .hazelrules imports. Unsupported Hazel features are surfaced for review and affected imported rules are disabled rather than run unexpectedly.
• Added a one-time Hazel migration assistant that detects Hazel, opens it, and guides users through exporting and importing rules.
• Expanded rule actions:
  • organize files by sorting into subfolders or synchronizing to another folder;
  • upload to FTP, SFTP, and WebDAV destinations;
  • add Finder comments, toggle extension visibility, toggle file locks, and create ZIP archives;
  • run AppleScript, JavaScript, and Automator workflows;
  • open files, reveal them in Finder, and create Finder aliases;
  • pause between actions, run rules on folder contents, continue matching later rules, display notifications, or ignore an item.
• Expanded rule conditions for Finder comments, file paths, folder item counts, last-opened dates, image dimensions, photo capture dates, PDF page counts, and arbitrary Spotlight metadata.
• Added a “match no conditions” rule mode.
• Improved the rule editor with visible action ordering, move controls, drag-and-drop insertion targets, and clearer enabled/disabled labels.
• Added a Settings preference to hide the menu bar icon while keeping Forel available from Finder or Spotlight.
  • Made Finder and Spotlight launches reliably bring the main Forel window forward.
• Added a View on GitHub link to the Settings About screen.
• Updated the rule list, README roadmap, changelog, persistence coverage, validation, preview, manual-run, and watcher tests for the new behavior.

Validation

• swift build
• swift test — 241 tests passed

[lguichard]

Hey! Thanks a lot for the PR and for all the work you put into this there are a lot of really useful additions here, and I really appreciate the contribution to Forel 🙏

The PR is quite large though, and it covers many different features at once, which makes it difficult to review and test properly.

Would you mind splitting it into several smaller PRs, ideally grouped by feature? For example, rule import/export and Hazel migration could be separate from the new actions/conditions, UI improvements, settings changes, etc.

That would make each change much easier to review, discuss, test, and merge independently.