VS 2022 (but not 2019) hangs if <TargetFrameworks> is defined in an include and overridden

[vsfeedback]

This issue has a corresponding ticket on Developer Community. Please vote and comment there to make sure your voice is heard.

---

[severity:It's more difficult to complete my work]

I encountered this by happenstance while adding a net6.0 build to a project (moving from 1 TFM to several). Since this is OSS, there's a public commit here illustrating (resolving) the issue: NickCraver/azure-webjobs-sdk@eed88b8

If you pull this branch/commit, VS 2022 will be happy. However, if you pull 1 commit back (NickCraver/azure-webjobs-sdk@2f6bf93 - totally unrelated change), you'll see VS 2022 will load 17/17 project and stall (I'm attaching a process dump from when it happened - I can reproduce this on every machine I have).

Notes:

• I thought this was <TargetFrameworks> in a base .props file and <TargetFramework> in a specific project resulting on both, but after switching everything inheriting that .props to <TargetFrameworks> the issue persisted.
• This issue doesn't happen in VS 2019 (also confirmed by another party) and seems to be specific to VS 2022.
• Most of the attachments here are from the running instance (post-fix) - I could not figure out how to attach to the hung VS in 2022, the feedback tool immediately launches the web version.

[haileymck]

fixed in #9256