AssertionScope w/explicit name AND DetermineCallerIdentity doesn't work as expected

[dennisdoomen]

Discussed in #2633

^{Originally posted by fuzzykiller May 6, 2024}
Sometimes, I'd like to provide human-readable context for a particular block of assertions. This however means that FluentAssertions no longer does its automatic assertion subject check. So instead of...

Expected instruction.Hidden not to be False, but found False.

I then get

Expected Instruction 3 not to be False, but found False.

That's not terribly helpful in my opinion. I can no longer see the property being checked. I'd like to have both: Explicitly provided scope name AND the automatic subject detection. Or maybe even, generally, a way for the resulting context name to be made up of all the nested (named) scopes along the way.

I see that AssertionScope is currently being redesigned, so maybe this here is a possible future improvement?