Introduce RepositoryInterceptor and Enable/DisableTracking() extension methods.

[maliming]

Added two extension methods so the developer can disable/enable entity tracking by these methods manually.

IDisposable DisableTracking(this IRepository repository)
IDisposable EnableTracking(this IRepository repository)

The EnableEntityChangeTrackingAttribute and DisableEntityChangeTrackingAttribute can be used by class/interface/method. The RepositoryInterceptor will get its Enabled property and change the current Tracking value by IEntityChangeTrackingProvider.

The Repository will check these conditions to decide whether to enable tracking.

• IsChangeTrackingEnabled (null by default. You can change it by DisableTracking or EnableTracking)
• The current Tracking value of IEntityChangeTrackingProvider . (It will be null if there is no EntityChangeTrackingAttribute)
• true by default.

Resolves #17487

Checklist

• I fully tested it as developer / designer and created unit / integration tests
• I documented it (or no need to document or I will create a separate documentation issue)

[codecov]

Codecov Report

Merging #17491 (9356884) into dev (51c742e) will decrease coverage by 0.05%.
Report is 1 commits behind head on dev.
The diff coverage is 41.04%.

@@            Coverage Diff             @@
##              dev   #17491      +/-   ##
==========================================
- Coverage   53.60%   53.55%   -0.05%     
==========================================
  Files        3025     3032       +7     
  Lines       94418    94604     +186     
==========================================
+ Hits        50610    50664      +54     
- Misses      43808    43940     +132     

Files Changed	Coverage Δ
...olo/Abp/Application/Services/ApplicationService.cs	82.69% <ø> (ø)
.../ChangeTracking/ChangeTrackingInterceptor_Tests.cs	0.00% <0.00%> (ø)
...eworkCore/Repositories/ReadOnlyRepository_Tests.cs	0.00% <0.00%> (ø)
...positories/EntityFrameworkCore/EfCoreRepository.cs	76.45% <66.66%> (-1.65%)	⬇️
...Domain/ChangeTracking/ChangeTrackingInterceptor.cs	78.57% <78.57%> (ø)
...olo/Abp/Domain/Repositories/BasicRepositoryBase.cs	52.32% <84.61%> (+5.02%)	⬆️
.../Abp/Domain/ChangeTracking/ChangeTrackingHelper.cs	89.65% <89.65%> (ø)
...lo/Abp/Domain/Repositories/RepositoryExtensions.cs	86.72% <93.75%> (+1.87%)	⬆️
...Injection/ServiceCollectionRepositoryExtensions.cs	100.00% <100.00%> (ø)
...p.Ddd.Domain/Volo/Abp/Domain/AbpDddDomainModule.cs	100.00% <100.00%> (ø)
... and 5 more

... and 4 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[hikalkan]

Inserting/updating/deleting an entity work even if you don't track changes for queried entities.

[maliming]

But the entity returned by the method or entity from parameters is no tracking after the method is called.

[hikalkan]

Where it is done? I didn't see any code part that detaches inserted/updated entities.

[maliming]

There might be code like this, So I think output warning logs are necessary.

using (var uow = uowManager.Begin())
{
    var author = await authorRepository.InsertAsync(new Author(Guid.NewGuid(), "Douglas"));

    // Entity still under tracking
    author.Name = "Douglas2";
    await uow.CompleteAsync();
}

[hikalkan]

So, in this example, author object is being tracked, and the name change is auto-saved, right? But the warning message says "Your changes may not be saved". Isn't that misleading the developer?

[maliming]

The code I share will not work if we disable entity tracking.
But developers may use such code, so I think we should output warnings when entity tracking is disabled.