Note: This is fundamentally working as intended, this issue is now about validating the config and providing a sufficient warning.

🐛 Bug Report

The configuration testSequencer (https://jestjs.io/docs/en/configuration#testsequencer-string) is silently ignored in projects (https://jestjs.io/docs/en/configuration#projects-arraystring--projectconfig)

To Reproduce

Run this config

It's common when writing scripts that install or configure things to need input from the user (at a minimum, something like 'Press Enter to continue'; at a maximum, to be able to prompt the user for input, with an optional default value, and return that value).

Let's use this issue to design how that would look, and I invite suggestions!

So I'm trying to set up my project with Jest/Spectator as it seems like a very neat way to develop tests but I'm running into issues with the dependencies for my components and services. And getting them mocked entirely isn't the main issue, changing their behavior to do different things is the main issue.

Say I have a service, that returns something, in my current tests that always seems to be

Describe the bug
When using the LMFineTuner and specifying the learning_rate_finder_configs , an error is thrown when passing these configs to finetuner.find_learning_rate() as suggested in the documentation and in the [Colab example](https://colab.research.google.com/github/Novetta/adaptnlp/blob/master/tutor

name: test
match: command
args:
  - var1

to

name: test
match: command
expose_args:
  - var1

This is consistent with expose_json_fields. So, any time we expose variable from within rules we would use the expose_ prefix.