Explicit versions in docker files
# What does this PR do?

@stas00 Here is the thread to discuss the version things in docker files.

- Objective:

  - We have more 3rd party libraries that depend on PyTorch version
  - Some of them need explicit versions, instead of using something like `$PYTORCH_VER`. For example, we have [1.11.200](https://www.intel.com/content/dam/develop/external/us/en/documents/ipex/whl-stable.html) in `intel_extension_for_pytorch-1.11.200+cpu-cp38-cp38-linux_x86_64.whl`
  - @stas00 suggest to specify the versions in the docker file(s), so we have better control.

- Implementation
  - The current attempt is not very good once we have more and more docker files, but so far it's OK.
  - If this is fine, I can **apply the same change to other docker files**.
@stas00 

Do you think we can keep `pip install torch` (latest release), and for 3rd party libraries, we use explicit versions?
(of course, we still need to update them when they have new releases)

Or you really prefer to set all of them (including `torch`) explicitly in docker file, and we update it when new release(s) are available?

WDYT, @LysandreJik <|||||>The reason I proposed to write out the explicit version is because the 3rd parties will fail if they are not adjusted (and of course provided the new builds) - so why not change everything in sync after validating the 3rd parties provide the new builds and not switch to the very latest until this happens.

So this is another good reason actually, if the 3rd party hasn't made a new build yet, after a new pytorch release, we shouldn't update pytorch.

Of course, this requires us to keep up to date with pytorch releases and act on it in a timely manner - e.g. for the last 3 pt cycles I asked torch-scatter owner to make a new release before updating our CI workflow files. <|||||>_The documentation is not available anymore as the PR was closed or merged._<|||||>For the record: 

Currently only `docker/transformers-all-latest-gpu/Dockerfile` is changed.

Since we don't install `intel_extension_for_pytorch` in other docker files (so far), and `torch-scatter` is fine with `torch` version, so I just keep as it is for now.