[KED-2453] Update large pipeline warning copy

[richardwestenra]

Description

1. Let's avoid saying "your pipeline" - we don't want to shame our users for their big-ass pipelines or make them look bad in front of a client. It's not a bad thing to be little on the large side, there's just more to love 😌
2. Let's inject a little levity and humanity into this message - studies show that even in corporate environments, when people use humour in the workplace, they are 23% more respected and are seen as more competent and more confident. Even executives have a sense of humour, they just don’t want us to imply that their work is of poor quality.
3. Let's use 'will' instead of 'might' - as @stichbury said, "I never like the 'might' word, because it implies doubt, and certainty is a nice thing for a reader."
4. Let's avoid needless repetition. There's no need to say "click to render", just show the button which says this anyway. Also, we prefer to avoid saying "click" because this implies that the user is navigating with a mouse, when they might be using a keyboard, touchpad or touchscreen.

Development notes

I've changed the max-width of the paragraph text to 30em, as this is the ideal width to split the two sentences onto two lines, and it is dependent on the font-size so the line-split will remain constant if the text size changes.

QA notes

Updated copy. The only thing worth checking is how this renders across screen widths and when the sidebar is open/closed.

Checklist

• Read the contributing guidelines
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added new entries to the RELEASE.md file
• Added tests to cover my changes

Legal notice

• I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

• I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.

• I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.

• I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

[studioswong]

Thanks @richardwestenra ! I am fine with both the previous copy and this one and will leave it up to @stichbury and @yetudada . I recall Joel mentioned about the tone of voice for the warning given we have to be mindful for client presentations, so might be worth checking in with him as well?

[datajoely]

I like it - let's ship it. Can we track how many times it's fired and the associated node count?

[richardwestenra]

@datajoely Thanks! We don't have tracking yet, but I'd love to track node/dataset/edge counts once we do.

[datajoely]

@datajoely Thanks! We don't have tracking yet, but I'd love to track node/dataset/edge counts once we do.

Render time would be great too