Remove "Refreshing..." output from top of plan.

[lkysow]

When running terraform plan, Terraform writes a line for each resource
it updates. For example:

null_resource.b: Refreshing state... (ID: 700288721293508840)
null_resource.a: Refreshing state... (ID: 2853194762920164292)
null_resource.f: Refreshing state... (ID: 6634469389761751950)

This change removes those lines by splitting the output string after a
separator.

This change is being made because the Refreshing output isn't important
and it will make the comments shorter.

From:

To:

Notes:

• This is thanks to suggestions from @jonboulle, @BlackTurtle123 and @majormoses
• This will help with Bitbucket server comments too long #280 and Formatting is broken when comments are continued on GitHub #111

[codecov]

Codecov Report

Merging #339 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #339      +/-   ##
==========================================
+ Coverage   70.63%   70.67%   +0.03%     
==========================================
  Files          61       61              
  Lines        3651     3655       +4     
==========================================
+ Hits         2579     2583       +4     
  Misses        893      893              
  Partials      179      179

Impacted Files	Coverage Δ
server/events/markdown_renderer.go	92.59% <100%> (+0.38%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6af4d79...16cdcf1. Read the comment docs.

[majormoses]

this will reduce a lot of headaches I have where developers are confused by the broken formatting and end up pinging me because they are not sure what to do. I have staged the changes and should be able to deploy tomorrow.

[majormoses]

Verified today that it works beautifully it prevented the splitting across comments on states where I know it has previously. We should probably still find a solution for it but it becomes a lot less urgent as you would need to do a lot of changes for it to show up and in those cases you can just make smaller pull requests.