Added salsaflow.yml.

Change-Id: cb10a54c6e
Story-id: IGNORED
Make sure we're sending an OK reply to RB.

RB is spamming us; it sends the same notification up to 4 times with little delays
so we're throttling them. We've been replying with HTTP 429 but that makes RB
fill the log with errors, so let's do HTTP 202 instead.

Change-Id: 8824f97459
Story-Id: SF-52
Transition issue to "reviewed" state if all reviews are approved.

We check JIRA issue's linked remote issues (which is how we link review
requests) to see if all reviews have been approved. We don't check RB because
RB's API is silly and does not allow searching by the `bug` field so finding
the review requests for a certain JIRA issue would be hard.

We don't check the initial state of the JIRA issue to be transitioned. We
assume that's JIRA's responsibility; the "mark as reviewed" transition is only
legal from the "implemented" state.

Change-Id: da725c0b13
Story-Id: SF-72
Update dummy issuetracker interface.

Change-Id: afa5558a99
Story-Id: SF-72
Removed invalid comment.

There's always at least one linked review because this function is called from
the review-published handler.

Change-Id: 3ccad2857e
Story-Id: SF-72
Made transitioning in review published handler  issue-type dependent.

Specifically, coding subtask now moves to `done` instead of `reviewed`.

Configurable by setting rules in config.
```
{
  issueTypeId: {
    required_state: "Id of the state the issue must be in",
    transition: "Id of the transition to the next state"
  }
}
```

Change-Id: 8f54b7c469
Story-Id: SF-72
Handle RB request discarding.

We delete the linked RR in JIRA when the relevant RR is discarded.
There will be a note of this action in the JIRA issue history so we don't lose
info.

Change-Id: d452d1a20d
Story-Id: SF-82