[bugfix] avoid the random shuffle of phoneme and tone tokens.

[XuesongYang]

What does this PR do ?

The order of outputs of dict.values() is usually shuffled so that the tokenizer and the model will be confused to match a correct sound for a specific integer index. You can tell the diff in between as below,

CTC Training Loss Curves
The upper and bottom curves are referring to the current implementation and bugfix, respectively.

Phoneme Token List

• current random order: ['#Q', '#VE', '#IE', '#X', '#Y', '#ZH', '#S', '#EI', '#ANG', '#V', '#O', '#H', '#D', '#F', '#T', '#G', '#OU', '#UI', '#UN', '#B', '#IU', '#I', '#C', '#AO', '#IN', '#L', '#^', '#M', '#ING', '#VN', '#Z', '#SH', '#EN', '#J', '#P', '#K', '#CH', '#AI', '#A', '#ENG', '#R', '#W', '#U', '#E', '#AN', '#N', '#ER', '#ONG']
• bugfix: ['#A', '#AI', '#AN', '#ANG', '#AO', '#B', '#C', '#CH', '#D', '#E', '#EI', '#EN', '#ENG', '#ER', '#F', '#G', '#H', '#I', '#IE', '#IN', '#ING', '#IU', '#J', '#K', '#L', '#M', '#N', '#O', '#ONG', '#OU', '#P', '#Q', '#R', '#S', '#SH', '#T', '#U', '#UI', '#UN', '#V', '#VE', '#VN', '#W', '#X', '#Y', '#Z', '#ZH', '#^']

Audio Examples

• current: https://drive.google.com/file/d/1w7SmNobbwx5g44M2uXff2Mrbkmy2lQAH/view?usp=drive_link
• bugfix: https://drive.google.com/file/d/1eROMHI5m4X1AZid-gryBnH99YGa85OI7/view?usp=drive_link

Collection: [Note which collection this PR will affect]

Changelog

• Add specific line by line info of high level changes in this PR.

Usage

• You can potentially add a usage example below

# Add a code snippet demonstrating how to use this 

Before your PR is "Ready for review"

Pre checks:

• Make sure you read and followed Contributor guidelines
• Did you write any new necessary tests?
• Did you add or update any necessary documentation?
• Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
  • Reviewer: Does the PR have correct import guards for all optional libraries?

PR Type:

• New Feature
• Bugfix
• Documentation

If you haven't finished some of the above items you can still open "Draft" PR.

Who can review?

Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.

Additional Information

• Related to # (issue)

[redoctopus]

Thanks for catching & fixing this! LGTM.