Implement map:for-each in default function library

[aj-stein-gsa]

User Story

Now that we have #266, I would like to request that we implement map:for-each per the related specification. It is not implemented at this time.

me@computer metaschema-java % ~/opt/bin/metaschema-cli --version              
metaschema-java 2.2.0-SNAPSHOT built at 2024-12-04T02:52:47+0000 from branch develop (55ee739) at https://github.com/metaschema-framework/metaschema-java
metaschema 2.2.0-SNAPSHOT built at 2024-12-04T02:52:47+0000 from branch develop (b6601f7) at https://github.com/metaschema-framework/metaschema.git
me@computer metaschema-java % ~/opt/bin/metaschema-cli metapath list-functions | grep map
In namespace 'http://csrc.nist.gov/ns/metaschema/metapath-functions/map' as 'map':
map:contains(map as map(*),key as meta:any-atomic-type) as meta:boolean
map:entry(key as meta:any-atomic-type,item as item()*) as item()
map:find(input as item()*,key as meta:any-atomic-type) as array(*)
map:get(map as map(*),key as meta:any-atomic-type) as item()?
map:keys(map as map(*)) as meta:any-atomic-type*
map:merge(maps as map(*)*) as map(*)
map:merge(maps as map(*)*,options as map(*)) as map(*)
map:put(map as map(*),key as meta:any-atomic-type,value as item()*) as map(*)
map:remove(map as map(*),keys as meta:any-atomic-type*) as map(*)
map:size(map as map(*)) as meta:integer

Goals

• Use anonymous function declaration for flexible map usage
• Allow flexible meta:map(*) processing in Metapath to process or transfer content on the fly

Dependencies

• Feature/anonymous functions #266

Acceptance Criteria

• All website and readme documentation affected by the changes in this issue have been updated.
• A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
• The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.

Revisions

No response

[wandmagic]

this is exciting