Add delve rewind/replay and core dump support

[brittblak4]

This PR will be imported into Gerrit with the title and first
comment (this text) used to generate the subject and body of
the Gerrit change.

Please ensure you adhere to every item in this list.

More info can be found at https://github.com/golang/go/wiki/CommitMessage

• The PR title is formatted as follows: frob the quux before blarfing
  • The part after the colon uses the verb tense + phrase that completes the blank in,
    "This change modifies Go to ___________"
  • Lowercase verb after the colon
  • No trailing period
  • Keep the title as short as possible. ideally under 76 characters or shorter
• No Markdown
• The first PR comment (this one) is wrapped at 76 characters, unless it's
  really needed (ASCII art, table, or long link)
• If there is a corresponding issue, add either Fixes golang/vscode-go#1234 or Updates golang/vscode-go#1234
  (the latter if this is not a complete fix) to this comment
• If referring to a repo, you can use the owner/repo#issue_number syntax:
  Fixes golang/tools#1234
• We do not use Signed-off-by lines in Go. Please don't add them.
  Our Gerrit server & GitHub bots enforce CLA compliance instead.
• Delete these instructions once you have read and applied them

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[lggomez]

Sorry, I made an earlier comment which I deleted. There is an original implementation on this PR at #89 but it is deprecated, is this PR derived from the original one for update reasons? That effort is deprecated as that functionality is being moved to the dlv-dap server

For the ongoing effort see its corresponding PR at #1268

[hyangah]

Thanks for the PR. As @lggomez said, the dev work is happening in go-delve/delve repo instead as we moved the default debug adapter to dlv dap.
@lggomez added the core/replay mode support which will be available in v0.27.1. Closing.

p. Work to support Record&Replay in mode=debug/test/exec is still a work in progress.