Added guideline about class modifiers, removed obsolete ones

[ViktorVoloshko]

Current guidelines have no mention about class modifiers and still suggest adding information about whether particular class can be extended or implemented in docs or in name of the class.

Using class modifiers makes that redundant.

Removed guidelines that recommend old approach, added new one that encourages to always use class modifiers.

Fixes #6437

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.
• This PR doesn't contain automatically generated corrections or text (Grammarly, LLMs, and similar).
• This PR follows the Google Developer Documentation Style Guidelines — for example, it doesn't use i.e. or e.g., and it avoids I and we (first person).
• This PR uses semantic line breaks of 80 characters or fewer.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Code changes should generally follow the Dart style guide and use dart format.
• Updates to code excerpts indicated by <?code-excerpt need to be updated in their source .dart file as well.