Remove the check for sequence number from P2TargetUtils.checkProfile

[laeubi]

Currently it is assumed that a profile is up-to-date if the sequence number does not change, but this has some risk to produce strange errors if for some reason there is no number or it is not changed. And even if the number changed, we still perform a check for actual changes.

Because of the constant problems in inconsistent behavior this now completely removes the check for the sequence number from the profile.

[github-actions]

Test Results

   285 files  ±0     285 suites  ±0   52m 12s ⏱️ -57s
 3 586 tests ±0   3 510 ✅ ±0   76 💤 ±0  0 ❌ ±0 
10 950 runs  ±0  10 719 ✅ ±0  231 💤 ±0  0 ❌ ±0 

Results for commit cd9649d. ± Comparison against base commit 6e21922.

[HannesWell]

In general this looks good and I appreciate the simplification.

But I wonder why this succeeds while #1540 fails a test. If possible I think it would better to make #1540 succeed as a whole.

[laeubi]

As both of @HannesWell and @merks expressed consensus here already that it is the right direction:

• Remove usage of the sequence number from target files #1540 (review)
• Remove usage of the sequence number from target files #1540 (comment)

and no test are broken I will merge this now so we can see if anything goes wrong with this smaller change.