feat: Migrate docs

[cpacker]

Migrating docs to readme.

Visible here: https://memgpt.readme.io/docs

Build process:

• Use the rdme CLI tool to sync docs from markdown to readme.com (one-way only, do NOT edit on readme.com without editing the source files, or the next sync will globber your GUI edits)
  • Install w/ npm install -g rdme (from here)
  • inside memgpt home directory, do rdme docs docs (format is rdme <type> <folder>)
• This is automated via the added github action

Review comments:

• Deprecate old docs? (should we maintain readthedocs domain and use redirects?)
• Figure out how to add GitHub link to readme.com
  • Current mkdocs has a cool viewer where it shows the current starts + links to GitHub
• Figure out what to do about editing
  • Previously on readthedocs you could click "edit" on the docs page and it would bring you to the github file editor
  • On readme.com, it will bring you to a login page, where a user can login to readme.com then propose an edit using their WYSIWYG markdown editor, which will open a "proposed change" ticket inside of the readme.com developer panel
  • One solution: disable propose edits button on readme.com, and explain how to edit on our contributor guide
  • Another solution: try and figure out a way to dynamically insert github raw file edit link into readme.com html (or manually do it?)
  • Third solution: just leave it, and manually handle edits that people submit in the markdown GUI editor (if any)

- [ ] Add API reference section to docs

• Big change, should put in later PR

[sarahwooders]

lgtm!