Track a remote branch for an MSC

Dieses Issue hat noch niemand übernommen.

#### Is your feature request related to a problem? Please describe.
In situations where the original author may want to delegate an MSC, and where - due to security reasons, or likewise - the author is unable to grant the delegate author access to the PR's origin repository, it may want to have the PR branch be updated from a remote branch instead, such as the delegate author's own fork.

In other situations, an organisation may want to - for legal reasons, or likewise - develop the commits on their own git server, but have them be fetched to the MSC's PR branch.

#### Describe the solution you'd like.
For these problems, I'd like the mscbot to be able to be set up to watch a remote branch. Be it on github, or on any compatible git server.

The original author of the PR has to setup the watch, via `@mscbot watch `.

After this, the MSC bot will only try to fetch commits from that branch via a `git pull`-like mechanism. That is to say; it will not force-push the PR branch with updates from the remote branch, it will only append new commits that were present in the remote branch, but not in the PR branch.

In other words, the MSC bot will only [fast-forward](https://stackoverflow.com/a/29673993/8700553) the PR branch to the remote branch.

Beginne mit dem Befehl `@mscbot watch ` und dem bestehenden Pfad des Bots zum Aktualisieren von MSC PR-branch; verfolge, wie Remote-Branches und fast-forward-Aktualisierungen behandelt werden. Als erledigt gilt, wenn ein konfigurierter Remote-Branch den PR-Branch ohne force-pushing aktualisieren kann, einschließlich Branches, die auf kompatiblen Git-Servern gehostet werden.

Vom Indexierungsmodell aus dem Issue-Text verfasst.