Extend tools selection syntax

[AhdraMeraliQB]

NOTE: Kedro datasets are moving from kedro.extras.datasets to a separate kedro-datasets package in
kedro-plugins repository. Any changes to the dataset implementations
should be done by opening a pull request in that repository.

Description

Fixes #3340

TODO: If merged after #3331 add docs changes as part of this PR

Simplified (or, well, shortened, at least) the validation regex

Development notes

Here's a breakdown of the regex to make reading this easier:

"^(all|none|(( )*(\\d*|\\d( )?-( )?\\d)(( )*,( )*(\\d*|\\d( )?-( )?\\d))*( )*))$"

Space repetition: ( )* -> any number of space characters

Component A: (\\d*|\\d( )?-( )?\\d) -> several consecutive digits or two digits separated by a hyphen with zero or one spaces on each side

Component B: (( )*,( )*(\\d*|\\d( )?-( )?\\d)) -> (( )*,( )*A) -> a comma surrounded by any number of spaces, followed by component A

Altogether: "^(all|none|(( )*AB*( )*))$"

The input all or none or an instance of A followed by any number of instances of B, with any number of space characters preceding or following them

Developer Certificate of Origin

We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a Signed-off-by line in the commit message. See our wiki for guidance.

If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.

Checklist

• Read the contributing guidelines
• Signed off each commit with a Developer Certificate of Origin (DCO)
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added a description of this change in the RELEASE.md file
• Added tests to cover my changes
• Checked if this change will affect Kedro-Viz, and if so, communicated that with the Viz team

[AhdraMeraliQB]

Here's how ChatGPT explains the new regex 🤖 :

Here's a breakdown of the key components:

• ^ and $: Anchors the regex to the start and end of the string, respectively.

• all|none: Matches either the string "all" or "none".

• (( )*(\\d*|\\d( )?-( )?\\d)(( )*,( )*(\\d*|\\d( )?-( )?\\d))*( )*): This part appears to allow for a combination of digits and ranges separated by commas. Let's break it down further:

• (( )*(\\d*|\\d( )?-( )?\\d): This part allows for either:

  • \d*: Zero or more digits.
  • \d( )?-( )?\d: A digit, optional spaces, a hyphen with optional spaces, and another digit.

• (( )*,( )*(\\d*|\\d( )?-( )?\\d))*( )*): This allows for zero or more occurrences of a comma followed by the same pattern as described above.

In summary, the regex allows for a combination of "all" or "none" or a sequence of digits and ranges separated by commas. The ranges can be specified as "X-Y", with optional spaces around digits and hyphens.

[DimedS]

Here's how ChatGPT explains the new regex 🤖 :

I'm also asking it to simplify that new regex without loss in functionality, and it provide that:
"^(all|none|( *\\d+)?( *- *\\d+)?( *, *(\\d+)?( *- *\\d+)?)* *)$"

looks like it make sense

[astrojuanlu]

You wrote a good explanation of the regex in the PR - can you actually include it here? Using re.VERBOSE:

https://docs.python.org/3/library/re.html#re.VERBOSE

[AhdraMeraliQB]

@DimedS

"^(all|none|( *\d+)?( *- *\d+)?( *, *(\d+)?( *- \d+)?) *)$"

I think this would allow an input of -4 or 1,2,-4 though, which we'd want to prohibit,

I'll test "^(all|none|( *\\d+)+( *- *\\d+)?( *, *(\\d+)+( *- *\\d+)?)* *)$"

[DimedS]

Thanks, @AhdraMeraliQB , very clear description, works well!

[merelcht]

LGTM! 👍 Great explanation.