[Feature]: Add support for map IDs in getTokens

[kwvanderlinde]

Describe the Problem

getTokens() can use a map name as a condition. But map names are neither stable nor unique, so map IDs are preferrable in many case. Alas, getTokens() does not support map IDs.

The Solution you'd like

Add a new "mapID" condition to getTokens() and getTokenNames() that will match maps by their unique ID.

Alternatives that you've considered.

Extending the existing "mapName" condition to support map IDs. I turned this down because "mapName" suggests a name not an ID, it makes matching less precise when map names look like GUIDs, and it could hamper any other future changes to map name lookups.

Additional Context

No response

[FullBleed]

Is there a way to pull functions that:

1. Currently only support mapname and not mapID.

2. Token specific functions that rely on currentMap instead of having a mapname/id parameter.

As someone painstakingly going through his primary framework and refactoring everything to be mapID aware I feel like all of the get* token based functions need to be updated to support mapID. As you noted, map names just aren't stable, and wide support for mapIDs wasn't available when I wrote, or incorporated, a LOT of features... But I'm running into situations where if I use functions that expect tokens to be on the currentMap (i.e. getLabel) I have to wrap sections of code in map switching.