### TL;DR
Added configuration file support for Zoom bot settings and improved meeting join process

### What changed?
- Introduced `config.json` for managing meeting credentials and bot display name
- Removed hardcoded Zoom URL and meeting parameters
- Added validation for meeting ID, password, and display name from config
- Simplified URL construction by removing the URL parser function
- Updated Dockerfile to copy the new config.json file

### How to test?
1. Create a `config.json` file with the following structure:
```json
{
  "meeting_info": {
    "meeting_id": "your_meeting_id",
    "meeting_password": "your_meeting_password"
  },
  "bot_display_name": "your_bot_name"
}
```
2. Run the container and verify the bot joins the meeting with the configured display name
3. Confirm the recording is still properly saved and uploaded to S3

### Why make this change?
To improve maintainability and security by moving meeting credentials out of the source code and into a configuration file, making it easier to update meeting parameters without code changes

Completes MEE-102