The SAL should not need to curate stack IDs

[bremoran]

There are several possible solutions.

• Linker tricks: each stack should place a symbol in a specific linker section. The index of the symbol is the stack ID
• String match: each stack defines an identifier string. The stack ID is the value of the pointer to the identifier string. Fallback is string comparison.
• yotta tricks: Similar to linker tricks, but instead yotta assigns a unique number to each module at build time. That number is the stack ID.

As user/partner-supplied stacks increase in number (e.g. due to external network modules) this will become more of a problem. One of the above solutions would be more effective.

[ciarmcom]

ARM Internal Ref: IOTSFW-1670