Generate api docs for getters

[devoncarew]

• generate api docs for getters (address part of docs: add property and event docs #190)

Done as a few commits for easier review (the bulk of the work is in the 2nd commit).

This PR also switches to generating getters before setters for a getter/setter pair. The convention is to document the getter, and this lets the code read as [docs] getter [setter].

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

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.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[kevmoo]

Awesome!

[kevmoo]

why change from function expression syntax?

[devoncarew]

I just found it more difficult to read and modify these methods as function expressions. I mostly stick with using them w/ trivial, ~1-line methods.

[kevmoo]

why no function syntax?

[kevmoo]

Why? Is nice!

[devoncarew]

I like the ability to decide whether to use them or not based on which gives the best readability. This lint complains all the time, even when the non-expression version reads better.