fix(fileflows): handle update API 401 and skip check on Node

[michelroegl-brunner]

✍️ Description

Fixes the FileFlows update command failing with curl: (22) / HTTP 401 when the server has security enabled.

• Server: Checks api/status/update-available with curl -sSL (no -f) so catch_errors does not trap on 401. On 401, shows a clear error asking the user to disable security in FileFlows or use the web UI, then exits. Otherwise uses the existing UpdateAvailable logic.
• Node: Skips the API check and always runs stop → backup → deploy → start (no server on port 19200).

🔗 Related Issue

Fixes #14622

✅ Prerequisites (X in brackets)

• Self-review completed – Code follows project standards.
• Tested thoroughly – Changes work as expected.
• No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

---

🛠️ Type of Change (X in brackets)

• 🐞 Bug fix – Resolves an issue without breaking functionality.
• ✨ New feature – Adds new, non-breaking functionality.
• 💥 Breaking change – Alters existing functionality in a way that may require updates.
• 🆕 New script – A fully functional and tested script or script set.
• 🌍 Website update – Changes to script metadata (PocketBase/website data).
• 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
• 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

[MickLesk]

that should be a little bit more, i forgot to add my pr and to push the latest fixes

main...fix/fileflows-node-update

i remember following:

1. Server = Serverside api call
2. Node = need an update in the calls

When a node is installed, the script runs dotnet FileFlows.Node.dll without a --server address, which creates an empty config and exits with "Configuration not set" every time systemd tries to start it. Per the docs, the node needs --server [SERVER_ADDRESS] to configure which FileFlows server to connect to

i think you should deploy the script and test it again