feat: add taplo completion spec

[batunpc]

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fixes #1532

What is the current behavior? (You can also link to an open issue here)
The completion spec does not exist for taplo

What is the new behavior (if this is a feature change)?
autocomplete will be supported for taplo

Additional info:
I used taplo --help as reference to work with all the subcommands and options. Also used the
taplo <subcommand> --help which produces different manual for each corresponding subcommands and option(s) in taplo.

Autocompletion for taplo in action;

[withfig-bot]

Overview

src/taplo.ts:

Info:

[withfig-bot]

Hello @batunpc,
thank you very much for creating a Pull Request!
Here is a small checklist to get this PR merged as quickly as possible:

• Do all subcommands / options which take arguments include the args property (args: {})?
• Are all options modular? E.g. -a -u -x instead of -aux
• Have all other checks passed?

Please add a 👍 as a reaction to this comment to show that you read this.

[fedeci]

Thanks @batunpc! I left some comments to solve before merging the PR, but overall it seems good to me!

[fedeci]

Suggested change

	suggestCurrentToken: true,
	suggestCurrentToken: true,
	template: "filepaths",

[batunpc]

Here template: "filepaths", is above the suggestCurrentToken
Would you like me to swap their places ?

[fedeci]

It is indifferent in a JS object. For styles we want to enforce we create eslint rules, so it npm run lint does not complain it is good to go!

[batunpc]

Thank you @fedeci I have addressed the requested changes in my last commit 9d4467f and left a comment for #1713 (comment)

[fedeci]

Thanks!