Remove remaining user-visible FileBot mentions

The full rebrand (session 9, seventh delivery) covered the app's own
identity - name, icon, no FileBot/FB-Mod branding visible - but two
literal "FileBot" mentions were still reachable by the end user, both
found via a targeted grep for FileBot/Filebot/filebot/FB-Mod across every
string actually rendered to a user (JSX text and CLI help/usage text),
as opposed to source comments and README documentation, which still
legitimately explain what this project is a rewrite of and aren't shown
inside the running app:

- The Naming Scheme editor's own inline help text described the FileBot-
  style short field names ({n}, {s00e00}, {t}, etc.) as "FileBot's own
  short field names" - reworded to just "Short field names", same
  meaning, no brand name.
- The CLI's -h/--help output described -non-strict as "Accepted for
  FileBot script compatibility" - reworded to "Accepted for compatibility
  with existing rename scripts".

Grepped the whole frontend and every Rust source string (not just these
two files) to confirm nothing else user-visible remained - tauri.conf.json,
Cargo.toml, and package.json were already clean. What's left after this
is exclusively source-code comments/doc-comments and README.md, none of
which the app itself ever displays.

Verified via cargo test --workspace (193/193, unaffected - text-only
change) + npm run build (clean).

src/components/RenamePanel.tsx

@@ -1695,10 +1695,10 @@ export default function RenamePanel() {
             need their own free API credential set there first). The separate Fetch Data button next to New Names
             still works on its own too, for re-fetching after changing the source or fixing a guessed name by hand. A
             batch can freely mix TV and movie files, even against different sources — each file only fills in the
-            fields that apply to it. FileBot's own short
-            field names (<code>{"{n}"}</code>, <code>{"{s00e00}"}</code>, <code>{"{t}"}</code>, <code>{"{y}"}</code>,
-            <code>{"{vf}"}</code>, <code>{"{vc}"}</code>, <code>{"{ac}"}</code>, <code>{"{group}"}</code>, etc.) still
-            work too, side by side with the names above.
+            fields that apply to it. Short field names (<code>{"{n}"}</code>, <code>{"{s00e00}"}</code>,{" "}
+            <code>{"{t}"}</code>, <code>{"{y}"}</code>, <code>{"{vf}"}</code>, <code>{"{vc}"}</code>,{" "}
+            <code>{"{ac}"}</code>, <code>{"{group}"}</code>, etc.) still work too, side by side with the names
+            above.
           </p>
           <p className="format-hint">
             Use <code>{"/"}</code> in the scheme to organize files into subfolders as part of renaming, e.g.{" "}