fix: pass download_config to LocalEvaluationModuleFactory calls

[aadhar-build]

Summary

Fixes #709.

Two call sites in evaluation_module_factory() that instantiate LocalEvaluationModuleFactory omit the download_config parameter:

# Before (both calls):
return LocalEvaluationModuleFactory(
    path, download_mode=download_mode, dynamic_modules_path=dynamic_modules_path
).get_module()

This means any custom DownloadConfig passed by the caller (e.g. custom token, proxies, retries, or cache settings) is silently dropped when loading local metric scripts. The same config is correctly forwarded when loading from the Hub via HubEvaluationModuleFactory.

Fix

Add download_config=download_config to both LocalEvaluationModuleFactory instantiations, matching the pattern already used for HubEvaluationModuleFactory:

# After:
return LocalEvaluationModuleFactory(
    path, download_config=download_config, download_mode=download_mode, dynamic_modules_path=dynamic_modules_path
).get_module()

This ensures that callers who pass a DownloadConfig (e.g. with use_auth_token, proxies, or custom user_agent) have that config respected even when the metric is loaded from a local path.