More efficient EntityId construction

The EntityId construction popped up in my profiling. No, it's not a bottleneck. Just called a lot of times. Which sums up a bit.

This actually changes:
* Inline one one-line private method.
* Check for string first (should be the most relevant case) and shorten out.
* What the legacy interpreter does is accepted and neither checked nor uppercased.