fix(map): avoid throwing required error if saving map of primitives with required: true

[vkarpov15]

Summary

If you create a map path using type: { Map, of: String }, you can store null values in that map. However, currently, if you try to set required: true on a map value path you get a validation error on map.$* whenever you try to validate a document.

Examples

[Copilot]

Pull Request Overview

This PR fixes a bug where maps with required schema values were incorrectly throwing validation errors on the internal $* path representation instead of validating the actual map entries properly.

• Adds logic to skip validation of $* paths which represent map schemas rather than actual document paths
• Includes comprehensive test coverage for the required validation behavior in maps
• Updates existing test to use async/await pattern for consistency

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
lib/document.js	Adds check to skip validation of $* paths in _getPathsToValidate function
test/types.map.test.js	Adds new test case for required validation in maps and updates existing test to async

Comments suppressed due to low confidence (1)

test/types.map.test.js:108

• [nitpick] The test name 'handles required in maps' is somewhat vague. Consider a more descriptive name like 'should validate required fields in map values' or 'should enforce required validation on map entries'.

  it('handles required in maps', async function() {