Document --exclude_rule

[naftali-g]

Naming convention:

• PRs for features that are in design should have the "proposal" label
• PRs for features that haven't landed yet should have the "future" label
• PRs for upcoming releases should have the "release" label
• PRs with new documentation for existing features should have the "existing feature" label

Before requesting review:

• Make sure there is a ticket in the DOC board in Jira
• Make sure CI is passing
  • Spell check failure may require adding backticks around code or updating spelling_wordlist.txt
  • See README.md for information about style and markdown syntax
  • If the CI Details link gives a 404, you need to log in to readthedocs.com
• Add link to generated documentation here
  • you can find this by following the read the docs link from the CI check
• Ask for help in #documentation

Jira ticket: TODO
Link to generated documentation: https://certora-certora-prover-documentation--393.com.readthedocs.build/en/393/docs/prover/cli/options.html#method

[johspaeth]

Thanks. Tiny suggestion for improvement to make the "when to use it" part more explicit.

[johspaeth]

Suggested change

	If there are specific methods for which a rule/invariant takes too long to run
	or require a different configuration.
	If there are specific methods for which a rule/invariant takes too long to run
	or require a different configuration, this config option allows to exclude it from verification.