Reorganize README for usefulness by user roles

[briandominick]

Fixes

• Fixes [Feature] Reorganize the README for user-friendliness #467 by @briandominick

Description

Rearranges the README doc so more technical/tooling/dev-related sections are toward the end, while content intended for "end users" is prioritized after setup instructions.

Also changed a few section headings and transformed sentence-case outliers to title case.

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the default branch of the repository (main or master).
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no
  visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[TimidRobot]

I think these changes are really helpful! Thank you!!

I only have two thoughts:

1. I think the "Code of conduct" section should remain at the top. It is important for issues, comments, etc., not just code submissions.
2. I am a little confused at "Project Usage" vs "Manual Usage". I think the sections might benefit from being combined or reorganized.

@briandominick please let me know if you'd like to discuss above two items before this PR is merged, or merge ASAP and follow-up. Either way works for me.

[briandominick]

I'll put the code of conduct back up top, and let me figure something out with the "usage" sections and I'll push again if you don't mind keeping this PR open a bit longer.

[briandominick]

Okay, sorry that took so long. The remnants of Debbie did some damage in my yard that I'm still cleaning up, and on top of that I switched laptops and had to get everything up and running on the new workstation.

My solve for the "Manual Usage" was just to get rid of that section heading. The original intent was basically "developer usage" vs "user usage" which is not necessary to highlight at that point in the document.

[TimidRobot]

Thank you!