testmo checks fails on community pull requests

[wojteknowacki]

PR from the community has no access to secrets, making testmo steps fail. I added the condition to trigger testmo only if the secret is available.

Screenshots

Pull Request Checklist

1. This code contains UI changes
2. All visible strings are translated with proper context including data-formatting
3. Attributes data-test-id are added for new elements
4. The changes are tested in Chrome/Firefox/Safari browsers and in light/dark mode
5. Your code works with the latest stable version of the core
6. I added changesets and read good practices

Test environment config

API_URI=https://automation-dashboard.staging.saleor.cloud/graphql/
APPS_MARKETPLACE_API_URI=https://apps.staging.saleor.io/api/v2/saleor-apps

Do you want to run more stable tests?

To run all tests, just select the stable checkbox. To speed up tests, increase the number of containers. Tests will be re-run only when the "run e2e" label is added.

1. stable
2. app
3. attribute
4. category
5. collection
6. customer
7. giftCard
8. homePage
9. login
10. menuNavigation
11. navigation
12. orders
13. pages
14. payments
15. permissions
16. plugins
17. productType
18. products
19. sales
20. shipping
21. translations
22. variants
23. vouchers

CONTAINERS=2

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6d649a8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR