$translate with `reverse=false` is trivial and can be supported

[axelv]

Passing reverse=false to translate operation fails because it is marked as notSupported(reverse). But if the value is false, nothing should change to the implementations.

Supporting this parameter is important for being compatible with other libraries like Pathling.

Related #315

[kaicode]

Hi @axelv. Initially we chose not to support the reverse flag because none of the maps SNOMED International publish should be used in reverse because the semantics become very blurry.

Are you saying that Pathling requires calling $translate with a reverse=false parameter? We could allow that.

[axelv]

@kaicode indeed Pathling is always including reverse so the default is reverse=false.
I fixed in my fork like this:
Tiro-health@05a6b58

I can create PR if you like it this way.

[kaicode]

Got it. Yes, your change looks good. A PR would be welcomed. Please create against the develop branch.