PollingController.startPollingByNetworkClientId does not type-check the given options

Nobody has claimed this yet.

When calling `startPollingByNetworkClientId` in a controller that inherits from PollingController, it is possible to not pass any `options` or the wrong `options`, even if types are supplied for those `options` in that controller's `_executePoll`. Since `startPollingByNetworkClientId` is contained with PollingController, and PollingController has no awareness of what a subclass needs, all it can say is that the `options` are optional, and if they are supplied, they must be `Json`. The result of this is that if options are missing from `startPollingByNetworkClientId`, it can cause errors at runtime, which is not only undesirable because it goes against the purpose of using TypeScript, but also because it it is confusing to consumers.

Start by locating PollingController and the subclass _executePoll declarations, then trace how startPollingByNetworkClientId types its options. Determine how the controller can preserve the subclass's required options and add compile-time coverage for missing and incorrect options. Done means invalid calls are rejected while valid subclass calls remain type-safe.

Written by the indexing model from the issue text.