Refactor configuration management by migrating to a modular config system

- Removed the old `infra.Config` structure and replaced it with a new modular configuration system in `pkg/config`.
- Introduced a `Config` struct in `cmd/web/config.go` to hold command-specific configurations.
- Updated configuration loading functions to utilize the new `LoadConfig` method with generics for type safety.
- Adjusted various initialization functions in `cmd/web/bootstrap.go` and `cmd/web/main.go` to reflect the new configuration structure.
- Cleaned up the `config.yaml` by removing obsolete fields and ensuring it aligns with the new configuration schema.

cmd/web/config.yaml

@@ -20,22 +20,6 @@ cache:
     db: 0
     pool_size: 10
 
-queue:
-  rabbitmq:
-    url: "amqp://guest:guest@localhost:5672/"
-    exchange: "tender_exchange"
-    queues:
-      scraping: "scraping_queue"
-      processing: "processing_queue"
-      notifications: "notifications_queue"
-
-search:
-  elasticsearch:
-    urls: ["http://localhost:9200"]
-    username: ""
-    password: ""
-    index_prefix: "tender_"
-
 user_authorization:
   jwt:
     access_secret: "your-super-secret-access-token-key-here-make-it-long-and-secure"
@@ -50,18 +34,6 @@ customer_authorization:
     access_expires_in: 3600 # 1 hour in seconds
     refresh_expires_in: 2592000 # 30 days in seconds
 
-ai:
-  openai:
-    api_key: ""
-    model: "gpt-3.5-turbo"
-    max_tokens: 1000
-  
-scraping:
-  user_agent: "TenderBot/1.0"
-  timeout: 30s
-  max_retries: 3
-  delay_between_requests: 1s
-
 logging:
   level: "info"
   format: "json"