Tests were failing in CI because the mock configs didn't include the new
rolling_deployment configuration. Updated both test files to include the
required configuration with default disabled state.

- Fixed tinyproxy Allow directive to properly support ONLY_HOST_IP configuration
- User_data.sh now defaults to restrictive access (127.0.0.1 only)
- Config.py handles both ONLY_HOST_IP=True (restrictive) and False (open to all)
- Removed duplicate rolling deployment status display from RollingConfig component
- RollingConfig now focuses solely on configuration, not status display
- Status information remains in ListProxies where it naturally belongs

This ensures secure-by-default proxy configuration while maintaining flexibility
and eliminates redundant UI elements for a cleaner interface.

- Updated test_providers_config.py to expect Allow 0.0.0.0/0 when only_host_ip=False
- Updated test_user_data.sh to reflect expected output with open access
- Tests now correctly validate the new behavior where proxies allow all IPs
  when only_host_ip is disabled

This ensures CI/CD tests pass with the updated proxy access control logic.

…ployment

- Fixed 12 tests failing due to rolling deployment preventing immediate deletion
- Added config["rolling_deployment"]["enabled"] = False to tests expecting immediate deletion
- Fixed age limit tests in AWS, GCP, DigitalOcean, and manager tests
- Created comprehensive unit tests for rolling deployment feature
- Achieved 98% code coverage for rolling.py module
- All 284 tests now passing (up from 272)