Prevent analyzer for transitive dependencies

Describe the bug

When adding Dapper.Aot on a project A, all project referencing project A will have the Dapper.aot analyzer enable and trigger the DAP001 on them.

I tried to play with PrivateAssets attribute of PackageReference but does not seem to work. Using PrivateAssets.All fail at runtime because the generated code use method defined in Dapper.Aot.dll

Where are you seeing this?

• Dapper.Aot 1.0.48

To Reproduce
See screenshot

Expected behavior
Have a way to not leak roslyn analyzer as transitive dependency.
I want to use the source generator in my lib. But not in other app that use my nuget package

Screenshots

Additional context
Dapper.Aot have been added to Hangfire.Postgres lib. But some people can use it as it enable Dapper.Aot in their app when referencing HF.PG nuget package

https://github.com/hangfire-postgres/Hangfire.PostgreSql/issues/416

Start by reproducing the Dapper.Aot 1.0.48 behavior with a project A and a referencing project, focusing on the PackageReference and PrivateAssets settings. Check how the analyzer and generated code are packaged, and verify that the analyzer no longer reaches transitive consumers while Dapper.Aot.dll remains available at runtime.