New rule S3363 (C#): Date and time should not be used as types for primary keys

[csaba-sagi-sonarsource]

Implement new rule S3363: DateTime and DateTimeOffset types should not be used as primary keys.

The rule raises an issue if: Entity Framework, or Entity Framework Core dependencies are found and a class contains a property of temporal type (DateTime, DateTimeOffset, etc.) that is either named Id, <type name>Id or decorated by the [Key] or [PrimaryKey] attribute.

• Implement Rule S3363 for C#
• Update RSPEC
• Create a basic C# implementation and basic test cases for .NET Core: DateTime, DateTimeOffset, TimeSpan
• Add test cases for EF 6.0 (.NET Framework)
• Add Test cases for TimeOnly and DateOnly types EF Core 7.0+)
• Skip validation if the project has no EF dependency
• Add test cases for [PrimaryKey] attribute (EF Core 7.0+)
• Optional: Add test cases for EF Fluent API (as FNs)
• Optional: cover temporal types from 3rd party libraries (like NodaTime)
• Optional: Add new ITs if necessary (if no IT covers the rule)

[zsolt-kolbay-sonarsource]

The DateOnly and TimeOnly types are also supported in Entity Framework Core 7.0 and above, so it's worth adding them to this rule.