Configure conflicting ARM baremetal cmake flags

[jathu]

Summary

Similar to #11457, but now we also want to warn against unsupported/conflicting flags. For example, when using EXECUTORCH_BUILD_ARM_BAREMETAL, we cannot enable certain flags.

Test plan

CI

$ cmake -DEXECUTORCH_BUILD_ARM_BAREMETAL=ON --preset macos

CMake Error at tools/cmake/common/preset.cmake:142 (message):
  Both 'EXECUTORCH_BUILD_ARM_BAREMETAL' and
  'EXECUTORCH_BUILD_EXTENSION_DATA_LOADER' can't be ON
Call Stack (most recent call first):
  tools/cmake/preset/default.cmake:352 (check_conflicting_options_on)
  CMakeLists.txt:87 (include)

cc @larryliu0820 @digantdesai @freddan80 @per @zingo @oscarandersson8218

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/11493

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (1 Unrelated Failure)

As of commit 8ce3d08 with merge base ce48e0d ():

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / android / run-emulator (gh) (trunk failure)
  The process '/usr/bin/sh' failed with exit code 255

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[zingo]

Thanks, if this combination don't work we should try to fix it :)

[swolchok]

Both 'EXECUTORCH_BUILD_ARM_BAREMETAL' and
'EXECUTORCH_BUILD_EXTENSION_DATA_LOADER' can't be ON

The ARM size test builds with EXECUTORCH_BUILD_ARM_BAREMETAL, and size_test.cpp requires FileDataLoader (and, currently, incorrectly doesn't enable it). Is it OK to remove this constraint?

[jathu]

@swolchok I'm not sure, you can try it. I tried retaining the existing behavior where EXECUTORCH_BUILD_EXTENSION_DATA_LOADER was turned off if baremetal was on