Reset the repository

[drewoldag]

Removing the ~50Mb example data file was a good thing, however, it's existence is still tracked in git history, as can be observed when cloning the repo (it's a 200Mb download).

Additionally, because this repo was created as a fork of the COIN-version of RESSPECT, every time a PR is created, the assumption is that we want to ultimately merge the code back into that COIN version.

The way to address both of these problems at this point (I believe) is to create a copy of this repo (i.e. clone it), delete this github repository, and then create a new repo with the same name, and push the copy up to the newly created repo. Doing so should create a fresh git history (without the 200Mb of example data floating around) and will make all new PRs default to merging into the new repo's main branch.

[mtauraso]

It may be worth noting that github offers the ability for support to remove the fork in the repository so long as you read their instructions (which will delete all issues and PRs) and say that won't work for you.

Request link: https://support.github.com/contact?tags=rr-forks&subject=Detach%20Fork&flow=detach_fork

Once de-forked, there is only the problem of the git history of the previous large file:
We could go a filter history appoach like these instructions which would require rebase from everyone using this repo, but we can likely skip the steps about asking github to remove cached data.