test(integration): use seleniarm

[JAdshead]

Description

The selenium image does not work on arm processor such as apples m1.
This changes from selenium to seleniarm standalone image to support running integration tests on systems with arm processor.

Added ONE_DANGEROUSLY_SKIP_API_IMAGES_BUILD flag to skip rebuilding api images for prod sample.

Motivation and Context

Contributors who work on new apple computers currently are unable to run the prod sample server and run integration tests locally.

How Has This Been Tested?

Locally with m1 and intel chips and integration test suite run through actions.

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (adding or updating documentation)
• Dependency update
• Security update

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• These changes should be applied to a maintenance branch.
• This change requires cross browser checks.
• Performance tests should be ran against the server prior to merging.
• This change impacts caching for client browsers.
• This change impacts HTTP headers.
• This change adds additional environment variable requirements for One App users.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using One App?

[github-actions]

Size Change: 0 B

Total Size: 712 kB

ℹ️ View Unchanged

Filename	Size
./build/app/app.js	164 kB
./build/app/app~vendors.js	411 kB
./build/app/runtime.js	7.07 kB
./build/app/service-worker-client.js	7.25 kB
./build/app/vendors.js	123 kB

_{compressed-size-action}