feat: update inline hints and tips

[tnolet]

I hereby confirm that I followed the code guidelines found at engineering guidelines

Affected Components

• CLI
• Create CLI
• Test
• Docs
• Examples
• Other

Notes for the Reviewer

• adds a hint on relevant reporters to use --record if the user did not use it when running test or trigger
• adds a copy & pastable hint on updating the CLI when there is a new version.
• small wording updates to other parts.

Resolves #1018
Resolves #973

[sorccu]

Tangentially related but we should really add that update warning for the create-cli. After you've installed it once it's basically guaranteed to stay the same version unless you lose your package cache somehow (by e.g. updating node). I guess we as the developers are more exposed to that rather than real users who might only ever run it once, but there may be some who try us out, leave, and then come back months later. If they just follow our docs (npm create checkly) it'll use whatever old version of the create-cli they already had installed and the user is not informed of that either. Worst case the version they had (and still have) is buggy, they see no improvement and they leave again. It would also be nice if our docs used npm create checkly@latest instead which would be another way to solve the problem.

[tnolet]

Tangentially related but we should really add that update warning for the create-cli. After you've installed it once it's basically guaranteed to stay the same version unless you lose your package cache somehow (by e.g. updating node). I guess we as the developers are more exposed to that rather than real users who might only ever run it once, but there may be some who try us out, leave, and then come back months later. If they just follow our docs (npm create checkly) it'll use whatever old version of the create-cli they already had installed and the user is not informed of that either. Worst case the version they had (and still have) is buggy, they see no improvement and they leave again. It would also be nice if our docs used npm create checkly@latest instead which would be another way to solve the problem.

I think we should indeed update all the links for to npm create checkly@latest. I will mark that on my list.

[tnolet]

@sorccu I've updated some parts to npm create checkly@latest where relevant. I will proceed to also update our docs site and the marketing site. Can you review when convenient?

[sorccu]

Looks good to me.

[sorccu]

But can you change the title to be more suitable for the changelog?