BlankSpruce

I'm not sure if it covers all the cases but here's something I've discovered: For current ryo-modal I couldn't recreate the first example provided in this issue but I can...

I'm not user of `vimish-fold` so it should be taken with a grain of salt but after a few quick tests it seems that this way to reformat buffer also...

@thisch Thanks for pointing that out. I've just checked how `insert-file-contents` behaves with origami folds in place and IMO it'd be worse than removing all the folds. Example with C++...

I've pushed another proposal. How about letting user decide how they want their buffer to be reformatted? By default it will be the current, fast implementation but they might either...

Just for the comparison I've extended `apheleia` locally to support clang-format: it actually works a bit better. Some origami folds might still get broken:  The first fold (line 2)...

I will consider that but there are certain caveats to work out: - Can I make it backwards compatible? I never liked the idea that upgrading formatter would require formatting...

I'm slowly moving my position to the following rule: "Use canonical name if it's official command or known custom command, otherwise lower case name". I'm opting for lower case instead...

I've implemented most of the stuff to support this feature but the remaining part is going through list of official commands and adding their canonical name. Here's an odd thing:...

@erijo If you were so kind to test the feature it's available [on this branch](https://github.com/BlankSpruce/gersemi/tree/canonical-casing). I've also extended [README about stub definitions](https://github.com/BlankSpruce/gersemi/tree/canonical-casing?tab=readme-ov-file#how-to-format-custom-commands-for-which-path-to-definition-cant-be-guaranteed-to-be-stable-eg-external-dependencies-not-managed-by-cmake) and in the [CHANGELOG](https://github.com/BlankSpruce/gersemi/blob/canonical-casing/CHANGELOG.md#changed) I've listed the commands...

I've released 0.13.0 along with fixes for other reported issues. Thanks for contribution.