Xlwings

- Avoid merge conflicts in `requirements` files when merging in upstream.

- Upstream GitHub Actions pipelines have been disabled on forks.
- Simplified dependency management by getting rid of separate Windows `requirements` files.

- Custom functions and custom scripts can now access the current user object by using a function parameter with the `CurrentUser` as type hint, see examples.
- Custom functions now work with thousands of concurrent requests.
- Upgraded dependencies incl. xlwings to 0.32.1.

- Added support for object handles: https://docs.xlwings.org/en/latest/pro/server/officejs_custom_functions.html#object-handles
- Added `staging` as additional environment name.
- Dependencies are now split up into `requirements-core.in`, `requirements-dev.in`, and `requirements.in` and managed via `python run.py deps`, see README.
- Added docker-compose production configuration under `docker` directory including Socket.IO and Redis services.
- More custom function examples.
- Bug fix: socket.io service now respects the `XLWINGS_APP_PATH`.
- Added `XLWINGS_SECRET_KEY` setting.
- Upgraded dependencies incl. xlwings to 0.32.0.

- Fixed an issue with custom functions when using the setting `XLWINGS_ENABLE_SOCKETIO=false`.
- Upgraded xlwings to 0.31.10.

- Fixed `utils.trigger_script()` to only trigger the script 1x no matter how many times the file is open.
- There is now an official Docker image available: https://hub.docker.com/repository/deployment/xlwings/xlwings-server
- Open Office.js alerts are now closed before showing a new alert, which would otherwise cause an error.
- Custom functions now show errors that happen outside the app, such as timeouts.
- Upgraded dependencies incl. xlwings to 0.31.9.