Update format of the pre go live checklist.

[helen-laktionova]

PR labels

When the PR is ready for review, add a TW review needed label. This lets us keep track of PRs that need to be merged and merge them in time.

PR Description

Describe the context for your changes and the changes you've made.

Tickets

If changes are associated with a ticket, add a docs ticket here.

Checklist

• I agree with the Code Contribution License Agreement in CONTRIBUTING.md

[vitaliiivanovspryker]

It would be very useful to have at least a direction for solving points, for example, what can and should be done in the code, what in the ABC account, or whether you need to create a support ticket or write to support, and what should be done within the customer's team, etc.

[vitaliiivanovspryker]

There are some recommendations such as following performance guidelines that are not initially applicable to this list but are general recommendations for the entire development process
Of course, no one will rework all the code right before the release, but we can recommend conducting an analysis in APM and fixing all the performance bottlenecks before the release

[vitaliiivanovspryker]

We also have a point about performance and volume tests without clarifying the criteria
It would be good to have at least a qualitative expectation for these tests