Fix PocoData Cache Issue

[Curlack]

Include Mapper Type in cache key for PocoData. Fixes #517.

Avoid "duplicate key" side effect in PocoData.ForObject method when handling dynamic objects.

[asherber]

@pleb I think this is ready for your review. Read the conversation thread only if you dare!

The gist is:

1. Add the mapper type to the PocoData cache key (as discussed in PocoData.ForType() caching #517)
2. Make the guard clause for dynamics in PocoData.ForObject() case insensitive, to avoid needless "duplicate key" error
3. Add a null propagator to the guard clause in Database.SetParameterProperties(), again to avoid needless errors with dynamics

[Ste1io]

Oh snap, you're committed now @Curlack! 🤣

Congrats on your first merge man.

[Curlack]

Thanks man