Added HTTPS support by configuring the application to use SSL certificates located in the root folder's `certs` directory. Users must place the `.key` and `.crt` files in this directory to enable secure communication.

… configure HTTPS in vite.config.ts

- Removed the `--https` option from the `runner.sh` script as it is not recognized by the Vite CLI.
- Configured HTTPS in `vite.config.ts` using environment variables to load certificate paths conditionally.
- Ensured the frontend Dockerfile builds without dependency on certificate files.

This resolves the issue of the frontend container failing to start due to the unrecognized `--https` option.

Updated the VITE_API_URL in the .env.EXAMPLE file to use HTTPS instead of HTTP to prevent mixed content errors. Also modified the API URL in api.ts to ensure all requests are made over HTTPS.

…igned certificates

- Updated all requests in the test suite to use verify=False to bypass SSL certificate verification.
- Ensured consistent use of verify=False across all HTTP requests in tests.

- Implemented SSL for secure communication between Orion and Gateway
- Added OAuth authentication for Gateway requests to Orion
- Gateway now sends an access token in the header for requests
- Currently using a mock access token as Orion authentication is not yet implemented
- To use SSL certification, create a folder named 'certs' in the root directory and put the certificate and key files inside it. The filenames should be 'mydev.key' and 'mydev.crt' for development purposes.
- Tested with a self-signed certificate

- Include USE_SSL_FOR_ORION in `settings.py` to configure SSL usage for Orion based on environment variable.
- Update `.env.EXAMPLE` to provide an example setting for USE_SSL_FOR_ORION, demonstrating how to enable or disable SSL.

…ovider

Implemented the integration of a real token provider for OAuth support, replacing previously used mock functions to enhance security and reliability.