Refactor app-layer persistence to typed repositories

[Copilot]

The app layer was coupled directly to IRepository<T>, which breaks down once features span multiple domain objects and relationships. This change moves the web/application layer to feature-oriented repositories while keeping the generic repository as a provider-level primitive for SQL, MongoDB, and RavenDB.

• Application-facing repository boundaries

  • Introduces typed repositories for the actual feature seams in the app:
    • IBlogPostRepository
    • ISimilarBlogPostRepository
    • IAboutMeRepository
    • IAnalyticsRepository
    • IBrokenLinkRepository
    • IShortCodeRepository
    • IBlogPostTemplateRepository
  • Keeps IRepository<TEntity> as the low-level storage abstraction behind those adapters.

• Typed adapters over existing providers

  • Adds thin repository adapters that compose the existing generic provider implementations rather than replacing them.
  • Preserves provider parity while moving query shape and orchestration closer to feature boundaries.

• Blog post caching moved to the typed layer

  • Replaces the special DI override of IRepository<BlogPost> with CachedBlogPostRepository : IBlogPostRepository.
  • Makes caching an explicit application concern instead of a one-off generic repository decoration.

• Provider health checks decoupled from content repositories

  • Introduces IPersistenceHealthCheck plus SQL / MongoDB / RavenDB implementations.
  • Removes the DatabaseHealthCheck dependency on IRepository<BlogPost>.

• Web/app consumers migrated off IRepository<T>

  • Updates pages, jobs, controllers, and services to depend on typed repositories instead of raw generic repositories.
  • Covers blog content flows, About Me, analytics, broken links, short codes, and blog post templates.

• Registration and dummy-data wiring

  • Registers typed repositories in AddStorageProvider.
  • Updates dummy-data setup to remove and re-register the new app-facing abstractions cleanly.

• Representative shape

  public sealed class BlogPostRepository(IRepository<BlogPost> repository) : IBlogPostRepository
  {
      public ValueTask<BlogPost?> GetByIdAsync(string id) => repository.GetByIdAsync(id);
  
      public ValueTask<IPagedList<BlogPost>> GetAllAsync(
          Expression<Func<BlogPost, bool>>? filter = null,
          Expression<Func<BlogPost, object>>? orderBy = null,
          bool descending = true,
          int page = 1,
          int pageSize = int.MaxValue) =>
          repository.GetAllAsync(filter, orderBy, descending, page, pageSize);
  }

This lays down the application-facing repository structure needed for richer content relationships such as series without pushing more complexity into the generic repository pattern.