Further update Optimization Detective documentation

[westonruter]

See #1857

[westonruter]

• Remove docs from the build.

[westonruter]

• Update introduction.md based on a new version drafted in a Google Doc.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.70%. Comparing base (42bd7a8) to head (7a5bfad).
Report is 12 commits behind head on trunk.

Additional details and impacted files

@@           Coverage Diff           @@
##            trunk    #1869   +/-   ##
=======================================
  Coverage   66.70%   66.70%           
=======================================
  Files          88       88           
  Lines        7029     7029           
=======================================
  Hits         4689     4689           
  Misses       2340     2340           

Flag	Coverage Δ
multisite	66.70% <ø> (ø)
single	37.20% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[felixarntz]

The current contents of the Google doc look good to me to move here. There may be small quirks here or there, but we can continue to finetune over time. This is excellent documentation and should provide a lot more context on how to use the plugin.

You probably need to still update the PR with the most recent changes from the doc, but I'm going to preemptively approve based on the doc contents.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: westonruter <westonruter@git.wordpress.org>
Co-authored-by: felixarntz <flixos90@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.