Update Getting Started Instructions and Settings

[RHammond2]

This PR addresses the third bullet point in #214 to improve upon the legibility of the getting started, contributing, and installation instructions. This is accomplished by a basic reorganization of the content to be more streamlined and by communicating the ideas more clearly and inline with using Python in 2023.

This also restructures the way that the examples are displayed so that can each be their own page on the documentation site instead of a single page with a high level of nesting.

[codecov-commenter]

Codecov Report

Patch coverage: 33.33% and no project coverage change.

Comparison is base (8d12083) 62.88% compared to head (1beafab) 62.89%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## develop_v3 #246 +/- ## =========================================== Coverage 62.88% 62.89% =========================================== Files 29 29 Lines 4209 4210 +1 =========================================== + Hits 2647 2648 +1 Misses 1562 1562 ``` | [Files Changed](https://app.codecov.io/gh/NREL/OpenOA/pull/246?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=NREL) | Coverage Δ | | |---|---|---| | [openoa/analysis/yaw\_misalignment.py](https://app.codecov.io/gh/NREL/OpenOA/pull/246?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=NREL#diff-b3Blbm9hL2FuYWx5c2lzL3lhd19taXNhbGlnbm1lbnQucHk=) | `84.77% <ø> (ø)` | | | [openoa/utils/imputing.py](https://app.codecov.io/gh/NREL/OpenOA/pull/246?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=NREL#diff-b3Blbm9hL3V0aWxzL2ltcHV0aW5nLnB5) | `90.41% <ø> (ø)` | | | [openoa/utils/machine\_learning\_setup.py](https://app.codecov.io/gh/NREL/OpenOA/pull/246?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=NREL#diff-b3Blbm9hL3V0aWxzL21hY2hpbmVfbGVhcm5pbmdfc2V0dXAucHk=) | `79.24% <ø> (ø)` | | | [openoa/utils/plot.py](https://app.codecov.io/gh/NREL/OpenOA/pull/246?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=NREL#diff-b3Blbm9hL3V0aWxzL3Bsb3QucHk=) | `4.81% <0.00%> (ø)` | | | [openoa/analysis/aep.py](https://app.codecov.io/gh/NREL/OpenOA/pull/246?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=NREL#diff-b3Blbm9hL2FuYWx5c2lzL2FlcC5weQ==) | `85.97% <100.00%> (+0.03%)` | :arrow_up: |

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[RHammond2]

@jordanperr, below are some replies as they relate to your bullets above, but separated for ease of cross referencing the original point.

• The installation instructions sit one step lower than the changelog because there are many considerations in terms of what a user might want from them, whether that's a basic user or someone contributing back to the repo. The chagelog, from my perspective also offers a lot of helpful information for getting started, particularly as we significantly update the repository. Additionally, the installation instructions having an extra click to get to the pip install prompt is largely in line with what many other code bases do that have varying options for what or how a user might want to install the package.
• At least when I build locally, it doesn't like to link to the actual example for some reason, and I think that has to do with the existing solutions to referencing examples that are contained outside of the documentation folder. The only way I can think of for getting around this issue is to hard code the link, but that will cause problems for others trying to access the different branches on the docs site because it will be hard-coded to a single branch's reference page. I'll update the naming convention as well, so it more clearly tracks the notebook naming.
• This tracks with Firefox as well, particularly for how it displays on the RTD vs a local build, which didn't have issues for me. I'll look into this, but I assume there is a setting that needs to be updated for a version change to properly allow for sideways scrolling.
• Good catch, this seems to be coming from our, not at all updated example modified-AEP example. I'll just update that in this PR per #247.