Configurable timeouts and concurrency limits via config.yaml

[yimsk]

Summary

Allow users to configure timeout values and concurrency limits through ~/.config/claws/config.yaml

Current Hardcoded Values

Constant	Value	Location
awsInitTimeout	5s	internal/app/app.go
multiRegionFetchTimeout	30s	internal/view/resource_browser_fetch.go
tagSearchTimeout	30s	internal/view/tag_search_view.go
metricsLoadTimeout	10s	internal/view/resource_browser_metrics.go
maxConcurrentFetches	50	internal/view/resource_browser_fetch.go

Proposed Config Structure

# ~/.config/claws/config.yaml
timeouts:
  aws_init: 5s
  multi_region_fetch: 30s
  tag_search: 30s
  metrics_load: 10s

concurrency:
  max_fetches: 50

Use Cases

• Slow network environments need longer timeouts
• Users with many profiles may want higher concurrency limits
• Debugging/testing may benefit from shorter timeouts

Related

• Adaptive auto-reload intervals + config-driven auto-reload and column visibility #46 (config.yaml infrastructure for auto-reload and columns)

[yimsk]

Related: #69 adding NO_PROXY endpoint list. Currently hardcoded with TODO(#67) marking config.yaml migration.

Proposed structure:

proxy:
  no_proxy_additions:
    - 169.254.169.254
    - 169.254.170.2  
    - 169.254.170.23

[yimsk]

Note: NO_PROXY config option out of scope

Per #69 discussion, claws will not touch NO_PROXY at all.

Therefore, config.yaml options like no_proxy_endpoints are unnecessary.