Handle error arrays like `AggregateError` for proper display

[gentlementlegen]

          maybe we should also handle `AggregateError` inside the SDK to have this functionality everywhere

Originally posted by @whilefoo in ubiquity-os-marketplace/command-start-stop#133 (comment)

Multiple aggregated errors do not get displayed properly by the SDK using postComment, because it is an array of errors instead of a single error with a single message. Error messages should get concatenated altogether.

[whilefoo]

Errors should be split by two empty lines \n\n and should not be prefixed with Error:

Example:

Warning

No price label is set to calculate the duration

This task does not reflect a business priority at the moment. You may start tasks with one of the following labels: Priority: 5 (Emergency)

[ubiquity-os-beta]

Note

The following contributors may be suitable for this task:

gentlementlegen

76% Match ubiquity-os-marketplace/command-start-stop#60

[ubiquity-os-beta]

Important

• Be sure to link a pull-request before the first reminder to avoid disqualification.
• Reminders will be sent every 3 days and 12 hours if there is no activity.
• Assignees will be disqualified after 7 days of inactivity.

[ubiquity-os-beta]

Passed the disqualification threshold and no activity is detected, removing assignees: @whilefoo.

[0x4007]

@whilefoo I thought you fixed this was there another similar problem and pull? I remember reviewing it.

[whilefoo]

Yes, I was waiting for #63 to get merged

[0x4007]

Looks like its merged.

[ubiquity-os-beta]

Important

• Be sure to link a pull-request before the first reminder to avoid disqualification.
• Reminders will be sent every 3 days and 12 hours if there is no activity.
• Assignees will be disqualified after 7 days of inactivity.