Special behaviour for temporal prefixes

[THardy98]

What was changed

Special behavior handling reserved temporal prefixes. Prevent users from:

• registering activities, task queues, signals/updates/queries with a reserved prefix
• calling default handlers with reserved names
• going through interceptors when calling internal queries

Note: this change does not cover handling reserved temporal prefixes for workflows, as it involves non-trivial changes to the workflow bundling.

1. Closes [Feature Request] Special behavior for Temporal built-in prefixes #1599

2. How was this tested:
   unit/integration tests

3. Any docs updates needed?
   I'm not sure.

[THardy98]

In this change, users are prevented from registering signals/updates/queries with reserved names from the handler.

Users can still defineQuery, defineSignal, defineUpdate that have reserved names. The reason for this is because we use defineQuery to create the reserved queries ourselves.

Alternatively, we can do the blocking in define<X> and create our internal queries/signals/updates using internal functions. Or we can do both (blocking in the define and the handler). I picked one because it seemed sufficient.

[THardy98]

this is blocked on #1640 so we can handle the same prefix cases for updates as well

[mjameswh]

At this point, taskQueue can be undefined. Won't that cause an NPE in throwIfServedName?

[THardy98]

I added a check but the WorkerOptions interface says that taskQueue can only be string