Tag names limitation

[boringbyte]

Description

Addresses https://github.com/kedro-org/kedro/issues/3727 This pull request was initiated to provide more information about valid node name and tag.

Development notes

make build-docs make lint

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

• [x] Read the contributing guidelines
• [x] 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
• [x] 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

[lvijnck]

@datajoely slightly off-topic, but why do we enforce such a strict requirement on the tag values? AFAIK they are exclusively used to run targeted portions of the pipeline. Why do we not keep them more flexible?

[datajoely]

@lvijnck short answer was it was causing errors in different places so we've simplified the space, what extra flexibility would you want?