Token2022 (extensions) support

[0xMMBD]

Add support for Token2022 instructions(extensions). Added:

• token2022 program id
• ProgramIdToken2022 enum value
• switch case to handle token2022 in message and transaction_printer
• extension names to the token instruction tag enum
• unit tests

[0xMMBD]

@sponomarev Hello, I've made some changes. Hopefully I didn't miss anything :) I've checked transactions with multiple instructions for old spl token as well as for the Token2022 and the same with simple examples like transfer. On my end it looked fine.

In my opinion the best way to handle this was to unify both token types as the same programId. Otherwise handling transaction_printers was getting a little tricky.

Let me know it there is anything else to change or if you find any other problems.

[0xMMBD]

The extensions are not supported currently. The main purpose of this PR was to properly handle basic operations on token when using Token2022 program. We wanted to make it backward compatible with existing features without the need of blind signing. So current extensions are recognized and are added in the code but we dont have any special logic for them This scope was discussed with @jnwng

[0xMMBD]

Hello @tiago18c can you please summarize what are the next steps? Is there anything else from our side that should be done?