[release/8.0] Improve the relationship cycle breaking logic to detect cycles even when not starting on one.

[AndriySvyryd]

Fixes #32422
Port of #32573 and #32593

Description

The issue here is that when looking for foreign key property configuration we only detected relationship cycles if the initial property was part of the cycle. The fix is to keep updating the marker property as we traverse the relationships in increasing intervals. Additionally, we now detect multiple relationship chains that end with incompatible conversions.

Customer impact

Exception when trying to use a model that has a relationship cycle with a dangling relationship. The intended workaround of specifying the configuration explicitly doesn't work with migrations as this configuration is not stored.

How found

Customer report on 8.0.

Regression

Yes.

Testing

Tests added.

Risk

Low and quirked.

[wtgodbe]

@AndriySvyryd can you get this reviewed? I can merge once it is

[maumar]

also ports HashHelpers introduced in #32124

[firasdarwish]

Hi @AndriySvyryd ,
I want to express my gratitude for your contribution.
I'd like to bring to your attention an issue I encountered with this feature in my project, which has 190 database entities
The validation and finalization time for the EF model is approx. 36 minutes on my i3-1115G4 (36 GB DDR4)
However, after disabling this feature using AppContext switch (Microsoft.EntityFrameworkCore.Issue32422), the time significantly reduced to it's original 3.5 seconds. It's worth noting that the project 'eventually' ran correctly in both scenarios, and I didn't encounter any memory issues like #33176