BTE doesn't recognize when a smartapi registration in its config list is not in the registry

[colleenXu]

This came up with the ICEES issue #421. BTE's config list at the time used smartapi registry IDs for ICEES APIs....but those registrations had been deleted. BTE didn't give any warning message (console or TRAPI logs) and continued working without using the ICEES APIs.

Is it possible for BTE to give a warning (in console/TRAPI logs), when a smartapi registry ID in the config list isn't found in the registry data? This would tell us devs that we need to review that entry in the config list...

[colleenXu]

For example, I can add the nonsense entry below to the config list, and I don't see a log in the console or TRAPI response that says that the nonsense API wasn't actually found in the registry

    {
        id: '455616156564',
        name: 'lalalala'
    },