Merge grafana/phlare repo into grafana/pyroscope

[simonswine]

Problem

End-Users, contributors and developers face a fair bit of confusion with the two projects and especially the wording of the Phlare README is misleading

Goals

• Keep commit history intact
• Ensure commit messages that reference to issues and PRs stay correct (Avoid that Segment Tree bug fixes #123 in a message from grafana/phlare will link to a different PR in the grafana/pyroscope repo)
• Do not loose the stars
• Be able to release OG and Pyroscope weeklies

The Plan

Phase 1

• Script to do the merge of the repos: Add repo merge script phlare#808

Phase 2: Move repo atomically

• Run the script on 2023-07-18 13:00 UTC, ensure PRs no longer can be merged into grafana/phlare, make Grafana Pyroscope available in the next branch, switch default branch to next.

Phase 3

Beta Give feedback

1. Improve README.md in both projects.
2. Sort out NPM dependencies #2000
   frontend +1
   
3. Rename phlare binaries to pyroscope Update binary name to pyroscope #2023
4. Move grafana/phlare docker image to grafana/pyroscope #2149
   6 of 6
   +0
   
5. @petethepig Clean up the og/ folder, decide what to keep what to remove and what to move out.
6. Determine the future of the pyroscope subcommands. (currently phlare only supports pyroscope server)
7. Migrate / delete og github workflows #2151
   0 of 21
   +0
   
8. Ensure the make generate works again @cyriltovena Fixes make generate #2140
9. Fix weekly builds @simonswine
10. tag api/ and ebpf/ folder
11. Merge and/or rename helm chart for pyroscope and phlare
12. Update MAINTAINERS.md

Phase 4

Beta Give feedback

1. Update examples
2. The og/ folder has disappeared
3. No code imports of github.com/pyroscope-io/pyroscope anmymore
4. First release of Grafana Pyroscope

[petethepig]

Little update from me, I deleted some things from /og directory, and started figuring out what to do with go packages (I will move some that we use and delete the rest). Here's the graph of dependencies: