Create an engine-tag-specific latest symlink

[rachael-george]

Issue:
The global latest symlink points to the most recent run regardless of engine or driver. When running multiple engines or driver configurations, there is no quick way to find the latest workspace for a specific engine-tag combination.

Fix:
After creating the global latest symlink, also create one under <workspace>/<engine_name>/<engine_tag>/latest pointing to the same workspace path.

Example structure:

  workspace/
  ├── latest -> .../2026_07_15_04_29_05                        # existing (global)
  └── functest/
      └── virtio-win-installer-Win2025x64_gui/
          ├── latest -> .../2026_07_15_04_29_05                # NEW (this PR)
          ├── 2026_07_14_10_16_43/
          ├── 2026_07_14_10_20_14/
          ├── ...
          └── 2026_07_15_04_29_05/

[gemini-code-assist]

Code Review

This pull request updates the workspace creation process in lib/project.rb to generate an engine-tag-specific 'latest' symlink in addition to the global one. The feedback suggests using a relative symlink target instead of an absolute path to prevent the symlink from breaking if the workspace directory is moved or renamed.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[kostyanf14]

Do not duplicate @config['workspace_path'], @engine_name, @engine_tag. Move this before @workspace_path = and then workspace_path = engine_base + timestamp, engine_latest = engine_base + 'latest'

[kostyanf14]

ok to test