fix: don't use localeCompare to compare string

[longngn]

localCompare behaves differently based on user's locale we got a few bugs recently because we use localeCompare to encode cost models, so some users get different script data hash