Slack step does not treat "\n" as a newline when message generated by a Bash script step

That said, even if that is how it is expected to work (from a technical point of view) if you generate the message from Bash, it might not be obvious and indeed might be unexpected.

To make it easier to work with the step, I created a PR for the Slack step which will now auto-convert the \ + n chars in a string to the \n escape sequence.

https://github.com/bitrise-io/steps-slack-message/pull/17/commits/cf1b8c5dde84d2716cdc350b6b35bb1a346ab8ac#diff-7ddfb3e035b42cd70649cc33393fe32cR125