chore: cleanup legacy code and add comprehensive test suite

[cloviscoli]

Summary

This PR removes obsolete .NET Framework and early .NET Core code, consolidates README documentation across all packages, and adds a comprehensive test suite covering all major framework components.

Key Changes

Removed Legacy Code

• NetFull/ directory: Removed all .NET Framework 4.x projects (Codout.Framework.Repository.EF6, Codout.Framework.Commom, Codout.Framework.Data, test projects)
• NetCore/Codout.Framework.Data/: Removed legacy DatabaseUtil.cs and DatabaseCore.cs (superseded by modern ORM implementations)
• NetCore/ repository projects: Removed obsolete Cosmos DB and DocumentDB implementations (Codout.Framework.NetCore.Repository.Cosmos, Codout.Framework.NetCore.Repository.DocumentDB)
• Codout.Framework.DP/: Removed deprecated data access layer project
• Shared/ directory: Removed legacy email configuration and shared project files
• appveyor.yml: Removed legacy CI configuration

Documentation Consolidation

• Simplified all package READMEs to concise one-liners describing the package's purpose and core contracts/interfaces
• Added new README files for previously undocumented packages (Codout.DynamicLinq, Codout.Framework.Domain, Codout.Image.Extensions, Codout.Multitenancy, security packages, etc.)
• Added ROADMAP.md and CONTRIBUTING.md for project governance

Comprehensive Test Suite

Added 40+ new test projects covering:

• Data layer: Repository and UnitOfWork contracts, entity abstractions, specifications
• ORM implementations: EF Core, NHibernate, MongoDB (CRUD, async, SaveOrUpdate, transactions, paging)
• Application layer: CrudAppServiceBase, service registration
• API layer: RestApiClient, HTTP extensions, exception middleware, DTO contracts
• Common utilities: String/DateTime/Numeric extensions, helpers (Inflector, SlugHelper, EnumHelper), security (crypto, hashing, random passwords)
• Domain layer: Entity equality, identity, value objects, audit/events, validation
• DynamicLinq: Filter/sort expressions, aggregates, grouping, datasource results
• Mailer: Service base, dispatchers (SendGrid, AWS SES), Razor template engine, health checks
• Storage: Azure Blob Storage, in-memory implementation, models and options
• Multitenancy: Tenant resolver, middleware, service registration
• Image extensions: Image processing utilities

Build & Infrastructure

• Updated .editorconfig with comprehensive C# style rules
• Added .github/dependabot.yml for automated dependency updates
• Added .github/workflows/codeql.yml for security scanning
• Updated .github/workflows/dotnet.yml and release workflows
• Added Directory.Build.targets for automatic README.md packaging
• Fixed UTF-8 encoding (removed BOM) across all modified files
• Updated Directory.Build.props with package metadata and documentation settings

Solution Structure

• Added new test project entries to Codout.Framework.sln
• Added new package projects (Codout.Framework.Api.Dto and Codout.Multitenancy folder structure)
• Reorganized project references for clarity

Implementation Details

• All test projects follow consistent naming (*.Tests.csproj) and use xUnit + FluentAssertions
• Test infrastructure includes fixtures for EF Core (SQLite in-memory), NHibernate (SQLite), and MongoDB (ephemeral replica set)
• README files are automatically embedded in NuGet packages via Directory.Build.targets
• UTF-8 encoding enforced across the codebase (no BOM, LF line endings)
• Removed all references to non-existent legacy namespaces and projects

https://claude.ai/code/session_01BnjVoHxcLymD2Mp9RcdG3u

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.