[types] Ensure string is checked before other types

[gregnazario]

Description

In Javascript, the types are erased, so inputs may not have the types associated. However, string can still be checked, so all inputs should first be checked for if it's a string, then fall back on other options.

This was often manifesting as:

"TypeError: Cannot read properties of undefined (reading 'startsWith')",
    "    at n.fromString (file:///var/task/node_modules/@aptos-labs/ts-sdk/dist/esm/chunk-BZMO6Q6L.mjs:1:422)",
    "    at n.fromHexInput (file:///var/task/node_modules/@aptos-labs/ts-sdk/dist/esm/chunk-BZMO6Q6L.mjs:1:879)",
    "    at new r (file:///var/task/node_modules/@aptos-labs/ts-sdk/dist/esm/chunk-NUBFOYQZ.mjs:1:1038)",
    "    at Runtime.handler (file:///var/task/index.mjs:42:57)",
    "    at Runtime.handleOnceNonStreaming (file:///var/runtime/index.mjs:1173:29)"

Test Plan

Tested by replacing one of the AccountAddress shortcuts with a toString()

Related Links

[0xmaayan]

I am confused about this change and if it is even a fix. Tests seem to pass if passing in a string/non-string from a js file before this change.
Also, the description error complains on passing in an undefined

[gregnazario]

I am confused about this change and if it is even a fix. Tests seem to pass if passing in a string/non-string from a js file before this change. Also, the description error complains on passing in an undefined

Yeah, this was my mistake.

The real question is if we want to bother protecting against undefined everywhere, or just leave it to the user to not mess up.