Reject indent and uppercase config options

[mosabua]

Fixes #981.

validateConfig already rejects options removed in version 10, but the version 5
removals were never added to that list, so indent and uppercase were accepted
and ignored. A config carried across the version 5 upgrade kept formatting
successfully while quietly falling back to the defaults.

This adds them to the same list, and turns it into a map so the error can name
the replacement:

indent config is no longer supported. Use tabWidth instead.
uppercase config is no longer supported. Use keywordCase instead.

It also rewords the shared message from "is no more supported" to "is no longer
supported", which reads better in English. That touches the six existing entries
and their assertions too, so say the word if you would rather keep the current
wording and I will drop that part.

I considered rejecting every unrecognized key instead, but that is a larger
behavior change and could break callers that pass extra properties. Extending
the existing list covers the upgrade path that actually breaks.

Tests added alongside the existing removed-option tests in
test/sqlFormatter.test.ts. Full suite passes locally: 27 suites, 5887 tests.

[mosabua]

One more instance of the same phrasing that I deliberately left out of this PR, since it is documentation rather than the error message this change touches:

https://github.com/sql-formatter-org/sql-formatter/blob/master/docs/paramTypes.md#L87

- `:1` numbered placeholders are no more supported

That is the only remaining occurrence in the repository outside node_modules. Happy to send a separate one-line PR for it if you want the wording consistent, or to fold it into this one. Just say which you prefer.