Migrate to ASP.NET Core 6.0

[i-rakityanskiy]

Steps to test:

1. Verify that application components work properly:

• Identity server
• Elasticsearch
• Google cloud storage
• Quartz
• Microsoft.CodeAnalysis.NetAnalyzers (replaced Microsoft.CodeAnalysis.FxCopAnalyzers)
• GRPC
• H3Lib
• Redis
• EmailSender

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
6 Code Smells

0.0% Coverage
0.0% Duplication

[ghost]

For what reason?

[i-rakityanskiy]

When the IndexFaker is used to generate Address.Id it causes an exception System.InvalidOperationException : The instance of entity type 'Address' cannot be tracked because another instance with the key value '{Id: 1}' is already being tracked. When attaching existing entities, ensure that only one entity instance with a given key value is attached.
I saw a workaround to avoid this exception here

OoS-Backend/OutOfSchool/Tests/OutOfSchool.WebApi.IntegrationTests/ProviderServiceIntergrationTests/ProviderServiceUpdate.cs

Line 43 in c906c60

fakeProvider.ActualAddress.Id = 5;

Using f.IndexFaker++ solves this.

[h4wk13]

It is not really good idea to change the generator trying to fix the problem with data.
Seems it was used in a wrong way.
It is better to find the reason why collection already contains the address with id 1

[i-rakityanskiy]

This happens because IndexFaker has an initial value of 0. When entity with Id=0 is added to the DB context, EF implicitly changes Id value to 1. When the second entity with Id=1 is generated and added to the DB context it causes the exception. I think that for the testing purposes that fix is sufficient enough. At the same time I agree that better solution can be found.

[i-rakityanskiy]

@h4wk13 Please check this PR #733