Ensure newline after trailing line comments to prevent formatting issues

[TTOzzi]

Resolve #1003

When arranging attributes, they were previously placed on a single line regardless of the presence of line comments.
This change preserves the original behavior of keeping attributes on a single line whenever possible, but inserts a newline when a line comment is present to prevent compilation failures.

[allevato]

Having to resolve this in the attribute case specifically feels like the wrong approach. There should never be a situation where a // or /// comment is followed by a break that would do anything but force a newline. Can you check that instead?

[TTOzzi]

Having to resolve this in the attribute case specifically feels like the wrong approach. There should never be a situation where a // or /// comment is followed by a break that would do anything but force a newline. Can you check that instead?

Thanks for the suggestion — I agree that it makes more sense to handle this through logic for // or /// comments rather than treating the attribute case separately. That should also help cover other cases we haven’t identified yet.
I’ll look into it again!

[TTOzzi]

I considered moving the test case to CommentTests, but it felt more appropriate to keep it where it is 🤔

[allevato]

I suppose this works, but I'm more worried about the token stream creation itself (I should have been more specific in my earlier comment). Usually the newline behavior is controlled by what kind of break is inserted into the token stream, and I would expect that a line comment would always be preceded by something whose newline behavior is soft (meaning always insert a newline, unless it would contribute more than the maximum number of blank lines allowed). The original issue would seem to imply that that's not the case, and I think we need to understand why.