Implementation of map:entry in default function library uses wrong return type

[aj-stein-gsa]

Describe the bug

As of commit 8b524d4 in develop, use of the map:entry function in the Metapath default function library implements the wrong return type, leading to a variety of Metapath processing errors in constraints.

Who is the bug affecting

Developers and engineers using map:entry and other related map-related functions for processing model-bound documents with Metaschema tools, particularly for constraints.

How do we replicate this issue

1. Use the map:entry function.
2. Debug the output of the function and observe a sequence of items that are not resulting in a meta:map(*) type.

Expected behavior (i.e. solution)

Map entries are properly created per the the related specification.

Other comments

No response

[aj-stein-gsa]

@david-waltermire I also reviewed all the function signatures for map: functions in the spec and they all look good after I double-checked. I set up #301 because that function is missing, but that is a different conversation for a different day.