Increase test timeouts only on CI env

[vmarta]

This PR gives some breathing room to the CI tests, so that any document queries or other things that may run intermittently slower can still finish without running into timeouts (timeouts from either react-testing-library or Jest).

In your local machine though, the tests should run much faster and thus not needing the increased timeouts there.

How to test the changes

To verify that local tests still fail fast with the default timeouts, try updating one of the Checkout tests like this:

// Inside the file app/pages/checkout/index.test.js
test.only('Renders skeleton until customer and basket are loaded', async () => {
    const {getByTestId, queryByTestId} = renderWithProviders(<Checkout />)

    expect(getByTestId('sf-checkout-skeleton')).toBeInTheDocument()
    expect(queryByTestId('sf-checkout-container')).not.toBeInTheDocument()

    console.time('FOO')
    try {
        await waitFor(() => {
            expect(getByTestId('FOO')).toBeInTheDocument()
        })
    } catch {
        // The above query should fail because FOO test id does not exist
    }
    console.timeEnd('FOO')
})

Then run the test by npm run test -- "./app/pages/checkout/index.test.js --no-coverage".
The FOO timer should last for around the default 1 sec (and not 6 seconds).

Types of Changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

• Removing a public function or component or prop
• Adding a required argument to a function
• Changing the data type of a function parameter or return value
• Adding a new peer dependency to package.json

Changes

• (change1)

How to Test-Drive This PR

• (step1)

Checklists

General

• Changes are covered by test cases
• CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

• There are no changes to UI

or...

• Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
• Changes comply with WCAG 2.0 guidelines levels A and AA
• Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

• Changes include a UI text update in the Retail React App (which requires translation)

[bfeister]

Nice 👍 🏅