feat: Add ability to customise type displays

[Sidnioulz]

This PR adds the ability to set the display characters for any action type. It works both for custom action types and for built-in ones.

Some notes:

• I didn't know how to name things; feedback is welcome here on the name the functions should have
• I first wanted to add a third parameter to setActionType to allow for setting both the type and the display together, but I am unsure of the consequences considering how loadAsset works in node-plop
• The Chinese README doc is missing

[crutchcorn]

I'll take a deeper dive later today, but I wanted to give initial feedback that this is one of the most comprehensive PRs I've ever received for the project.

Deeply appreciate that not only did you change the code, but you:

• Modified existing tests
• Added new unit tests
• Added new E2E tests
• Wrote docs

Honestly just all around 👏👏👏

[Sidnioulz]

I'll take a deeper dive later today, but I wanted to give initial feedback that this is one of the most comprehensive PRs I've ever received for the project.

Least I could do considering the many days your project saved me! I wrote a codegen CLI by hand in the past and I can appreciate how useful Plop is. Looking forward to your review!

[Sidnioulz]

• Add missing type defs in node-plop and reexport them in plop

[Sidnioulz]

Hi @crutchcorn, just in case you're waiting for me to take care of the above task to do a review, I'm waiting for a review to make batch fixes to the branch 😅

[crutchcorn]

Overall this code looks awesome @Sidnioulz - apologies for the massive delay in the review.

If you want to finish up the last remaining tasks I'll merge this ASAP :)

[Sidnioulz]

Overall this code looks awesome @Sidnioulz - apologies for the massive delay in the review.

If you want to finish up the last remaining tasks I'll merge this ASAP :)

Thanks, I think it should be done now. I've reformatted (amended the initial commit) and added type declarations to the NodePlopAPI (separate commit).

Leaving this in your hands :-)

[Sidnioulz]

Hi @crutchcorn, any chance you look at this in the coming weeks?

To the best of my knowledge, the windows-latest, 16 test was broken on main and unrelated to this branch. I've force-pushed the exact same code to re-trigger the workflow and check the test logs, as they've expired since I last committed.

Besides that, do you need help maintaining this package?