Fix Cargo version parsing for workspace inheritance syntax

[zahidblackduck]

JIRA Ticket

IDETECT-4925

Description

Both Cargo detectors were failing to parse name and version from Cargo projects using workspace inheritance syntax (version.workspace = true). For example, a valid Cargo.toml,

[workspace]
members = ["extra-lib"]
resolver = "2"

[workspace.package]
version = "0.5.0"
edition = "2021"
repository = "https://github.com/example/repo"

[package]
name = "root-app"
version.workspace = true
edition.workspace = true
repository.workspace = true

The CargoTomlParser was incorrectly assuming version to be a string, but in cases of workspace inheritance, version is represented as a toml table. This caused TomlInvalidTypeException during dependency extraction.

Proposed Fix:

• Updated CargoTomlParser to detect when version is a table and handle workspace inheritance correctly.
• Added unit tests to validate parsing of Cargo.toml files with version.workspace = true.

Note: This is meant to be shipped with detect 11.2 release.

[devmehtabd]

What do we want to do for conditions when versionObj is null, I have seen examples in python where version is not specified, do we have similar concept in Cargo?

[zahidblackduck]

That's an interesting question which I didn't think of earlier. I'll explore further whether there is any possibility of an version section being null and if so, then how cargo declares / handles this.