Better customtext management

[Andre601]

Right now any /customtext value is stored inside a single custom.txt file.

This feels extremely weird as you have to deal with a somewhat unusual system for creating different chapters (Using #text for chapters) and also suffering the problem that text is auto-paginated if it goes beyond 9 lines.

My suggestion is to update the system to use a dedicated customtext folder, where each chapter would be its own file to manage.

In addition could the files allow the usage of settings through a YAML-frontmatter like formatting to change stuff like the split/pagination behaviour.

As an example, if I want to make a /customtext voting command that prints a text without any pagination, I would make a customtext/voting.txt file with the following content:

---
split: -1 # -1 tells Essentials to not split at all
#name: vote # Optional. Override the name used for the subcommand
---
Vote for our amazing server and receive 10 coins for each vote!

Vote Site 1:
https://someamazingvotesite.com/server/myserver/vote

Vote Site 2:
https://anothervotesite.com/servers/myserver/vote

Vote Site 3:
https://vote.example.com/mc/myserver

This would print all lines without any pagination when using /customtext voting

Additionally, to make the creation of new TXT entries easier could perhaps a --create option be considered?
It would essentially create a bare-bones example using the provided name as file name. I.e. /customtext newtext --create would create a file called newtext.txt
Alternatively could it be its own dedicated command (or you would use a specific subcommand, but that may break existing setups)