[bare][ci] Remove native-component-list from bare-expo if running on the CI (#7170)

# Why

Since I added `native-component-list` to `bare-expo` app (#6868), tests are sometimes failing due to time

[bare][ci] Remove native-component-list from bare-expo if running on the CI (#7170)

# Why

Since I added `native-component-list` to `bare-expo` app (#6868), tests are sometimes failing due to timeouts. It mostly refers only to the first test suite because it's the first to trigger code bundling. Excluding `native-component-list` code from `bare-expo` when it's run on the CI should solve the problem or at least reduce code bundling time.

# How

If `process.env.CI` or `process.env.NO_NCL` is truthy, then we will use custom resolver for all imports from `native-component-list` - the custom resolver will simply return `null` - so its main navigators won't be included in the bottom tabs navigator.

# Test Plan

- `yarn run test:web` in `apps/bare-expo` works locally and I see `native-component-list` paths in webpack's logs and the total time for `Basic` tests is high.
- `CI=true yarn run test:web` also passes and takes significantly less time.
- `yarn run ios` works as expected.
- `CI=true yarn run ios` works as well, with just `test-suite` app included.
- `sdk/web_test_suite` passes and bundling time is much better now.

show more ...