Support bothToken and WECHATY_PUPPET_SERVICE_TOKEN envrionment variable name

[wj-Mcat]

I always be annoyed about WECHATY_PUPPET_SERVICE_TOKEN name which is too long and hard to write.

On the one hand, there is only one type of token name for polyglot wechaty, so every token name has the same impact. In other ways, TOKEN and WECHATY_PUPPET_SERVICE_TOKEN are the same for polyglot wechaty. If there are many type of tokens, we should use different token name to differ endpoint. But, hostie server can help us discover the endpoint.

On the other hand, we should always keep it simple for wechaty to use token. TOKEN is more simpler than WECHATY_PUPPET_SERVICE_TOKEN in the length of text.

So, I suggest that wechaty should support TOKEN and WECHATY_PUPPET_SERVICE_TOKEN envrionmnet variable name to set token.

@huan How do you think about ?