Add recaptcha_{private,public}_key_path config option

[V02460]

Another config option on my quest to a *_path variant for every secret. Adds the config options recaptcha_private_key_path and recaptcha_public_key_path. Tests and docs are included.

A public key is of course no secret, but it is closely related to the private key, so it’s still useful to have a *_path variant for it.

Pull Request Checklist

• Pull request is based on the develop branch
• Pull request includes a changelog file. The entry should:
  • Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from EventStore to EventWorkerStore.".
  • Use markdown where necessary, mostly for code blocks.
  • End with either a period (.) or an exclamation mark (!).
  • Start with a capital letter.
  • Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry.
• Code style is correct
  (run the linters)

[MadLittleMods]

We can dumb this down a bit:

Suggested change

	You have configured both `recaptcha_private_key` and
	`recaptcha_private_key_path`. These are mutually incompatible.
	You have configured both `recaptcha_private_key` and
	`recaptcha_private_key_path`. Only one or the other can be specified at a time.

[MadLittleMods]

This is a slight variation on the typical error message we've been using for this:

Conflicting options 'macaroon_secret_key' and 'macaroon_secret_key_path' are
both defined in config file.

I like the version that this PR has but we should probably be consistent and update all the other similar errors.