feat: Add Lineage Enablement Cache

[utkarsh-goel-google]

Description

This pull request introduces a new caching mechanism for Lineage Enablement and significantly refactors the existing cache implementation to
improve maintainability and reduce code duplication.

Key Changes:

• New Lineage Enablement Cache:

  • A new cache has been added to handle PERMISSION_DENIED errors with LINEAGE_INGESTION_DISABLED reason that occur when Lineage is not enabled for a project and client.
  • This prevents repeated API calls to projects where Lineage ingestion is known to be disabled, improving client performance and reducing
    unnecessary network traffic.
  • Note: The Lineage ingestion enablement is controlled via Lineage Configurations per client.

• Refactoring to a Generic Cache Model:

  • The duplicated logic between the original API Enablement Cache and the new Lineage Enablement Cache has been eliminated.
  • A single, generic ProjectStatusCache class has been created to handle the core caching logic using a composition-based design.
  • The specific cache implementations (StandardApiEnablementCache and StandardLineageEnablementCache) now act as simple, lightweight
    wrappers around this generic component.

• Consolidated Cache Configuration:

  • The previous configuration classes (ApiEnablementCacheOptions, ApiEnablementCacheSettings) have been
    removed and replaced with two generic classes: CacheOptions and CacheSettings.
  • This centralizes all cache configuration, making the system cleaner and easier to manage. The original Api... classes were effectively renamed and generalized to Cache... to reflect their new, broader purpose.

[KonstantinMi]

Looks good