[test] add CI workflow for VCS installation

[XuehaiPan]

What does this PR do?

Add a CI test for checking VCS installation (via URL or git repo). This workflow prevents potential breakage for install from source installation method.

Ref:

• [setup] migrate setup script to pyproject.toml #22539
• Revert migration of setup to pyproject.toml #22658
• No module named 'transformers' after installing from source #22599

Before submitting

• This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
• Did you read the contributor guideline,
  Pull Request section?
• Was this discussed/approved via a Github issue or the forum? Please add a link
  to it if that's the case.
• Did you make sure to update the documentation with your changes? Here are the
  documentation guidelines, and
  here are tips on formatting docstrings.
• Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

[XuehaiPan]

Maybe also add test for macOS and Windows. But I think it would be unnecessary. The wheel for transformers is platform-independent (the dependencies are platform-dependent).

[sgugger]

Or we can just leave the setup as is and there won't be any need for this new check :-)

[XuehaiPan]

Or we can just leave the setup as is and there won't be any need for this new check :-)

The CI workflows in this PR can also benefit to check the viability of transformers' dependencies.

I think the ultimate solution is to ask the user to upgrade their pip first in the documentation:

pip install --upgrade pip setuptools  # upgrade to support PEP 660
pip install git+https://github.com/huggingface/transformers

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread.

Please note that issues that do not follow the contributing guidelines are likely to be ignored.