Add search option for relating message id to route

[skliper]

Is your feature request related to a problem? Please describe.
Core implementation is message id == message key, leading to a large, sparse message table to get the route index.

Describe the solution you'd like
Eliminate message table. Order routing table by ID and binary search, or other search options (optimal solution may depend on configured sizes such as number of supported message IDs and number of supported routes).

Describe alternatives you've considered
See also #929, hash.

Additional context
Allowed by #928

Requester Info
Jacob Hageman - NASA/GSFC