Always expand coverpoint statements

[sriyerg]

Test case

  // Input to the formatter, preferably a reduced test case.
  cp_handshake_complete: coverpoint status {
    bins complete = {AlertAckComplete};
  }

Include any options or configuration used.

Actual output

  // This doesn't look right.
  cp_handshake_complete: coverpoint status {bins complete = {AlertAckComplete};}

Include any possible diagnostic messages from the formatter.

Expected or suggested output
Original is better.

Citations to published style guides would help.
Don't have one yet (I think), but will add soon.

[snsokolov]

Citations to published style guides would help.

Not sure about other style guides, this not regulated by the internal style guide.

It looks to me that formatter is trying to keep short statements like this on one line to make it more concise, but +1 that the original is looking more readable.

[msfschaffner]

If we decide to always expand coverpoints, it probably makes sense to do the same for constraints as well for consistency (as indicated by @sriyerg here: #445).

[fangism]

General drive-by comment:
When there is a request to expand a section, the first thing I ask is whether a well-placed //comment can force that expansion, without having to add a control switch -- clang-format respects comments to force expansion in many places. Some of the formatter logic is intended to respect comments to do that. I understand that some users don't want to add extra comments.