fix(update): set CastError path to full path if casting update fails

[vkarpov15]

Fix #14114

Summary

Currently, CastError only shows the path relative to parent, which is less than ideal in the case where casting update throws an error; in that case, Mongoose just throws the CastError, rather than wrapping the CastError in a ValidationError like how save() does. This PR makes CastError use $fullPath instead when casting updates

Examples

[hasezoey]

Code looks good to me, though what about other types like uuid or Decimal128 or does this only apply to this.applySetters calls?

[vkarpov15]

@hasezoey this change is just for castForQuery(). Decimal128 uses SchemaType base class's castForQuery, so that's covered. It looks like uuid isn't using applySetters() though, I'll check.

[hasezoey]

Code looks good to me, though it seems deno does not like the UUID change

[vkarpov15]

@hasezoey the deno issue looks unrelated, it's an unfortunate quirk with how our tests are written: Test.findOneAndUpdate({ _id: doc._id }) is equivalent to Test.findOneAndUpdate({}, { _id: doc._id }) because findOneAndUpdate() with 1 arg means Mongoose treats the 1 arg as an update parameter, not a filter. Which means that, if there's any dangling data in the underlying collection, the test will fail. I'm not sure why there's dangling data in deno tests here, but either way we should improve the tests to make them more durable, which I did in 6f7b659