csproj replacement updates wrong XML nodes

[NecatiMeral]

Hey everyone,

thanks for providing such a powerful extension. We're using it extensively and it makes my DevOps-journey much simpler.
When attempting to create CI/CD pipelines for some of our .Net-Framework (4.8) applications, I've noticed that the version replacement in the csproj files is a little too lax.

We have a kind of dotnet monorepo which hosts our internal framework code. A new package version is created for all packages at once.
We have a Directory.Build.props which specified the version at a repository wide level like this; this gets replaced as expected:

Unfortunately, in the project files, the PackageReference's version value gets replaced also, which thankfully breaks the build:

Proposal:
Since I think there are valid scenarios for this kind of replacement, can you provide a toggle to exclude PackageReference nodes?