[GHA] test install

[AlexanderDokuchaev]

Changes

Add workflow "Test install"

• Add removable_tmp_path to clean venv after test, to avoid reach space limit on host.
• Remove test_install_with_tests_requirements
• Check only python -m venv
• Split 'helper.py' to run install test without install pip install -e .

Tests

run

[alexsu52]

I would suggest to apply nightly schedule to the install tests, taking into account time of tests

The install tests should be able to run manually.

[AlexanderDokuchaev]

@alexsu52 @MaximProshin what you think about 2 triggers for test install:

1. nightly: full test cpu, gpu, all type of installation, linux and windows
2. post_merge: only cpu, only one build_s, only linux

Or second trigger can be used as precommit (will be fast test)

[MaximProshin]

@alexsu52 @MaximProshin what you think about 2 triggers for test install:

1. nightly: full test cpu, gpu, all type of installation, linux and windows
2. post_merge: only cpu, only one build_s, only linux

Or second trigger can be used as precommit (will be fast test)

@AlexanderDokuchaev , why do you want to have some checks post merge? Do we often break smth here?

[AlexanderDokuchaev]

@MaximProshin not often, but it's cheap, simple, it save time of developer who will investigate falls

[alexsu52]

@AlexanderDokuchaev I would consider to add the fast test to the precommit. This solution looks better than introducing post-merge phase but dependent on test time. Could you share test time of only cpu, only one build_s, only linux?

[AlexanderDokuchaev]

https://github.com/openvinotoolkit/nncf/actions/runs/12001473810

[alexsu52]

LGTM