Add flags in conformance tool to accept implementation metadata

[AnupamGhosh]

This issue tries to solve the 4th point in #138 for capturing the metadata about the conformance report submission

To support an automated conformance reporting workflow, the conformance testing tool needs to capture details about the specific implementation running the tests.

Add the following optional CLI flags to the conformance tool:

1. --organization (e.g., Google, Submariner)
2. --project (e.g., GKE, Submariner Multi-cluster)
3. --version (e.g., v1.2.0)
4. --url (Link to the project or implementation docs)

With these flags, the tool will populate an implementation metadata section within the generated YAML report, similar to how gateway-api does in their report.
Embedding the metadata directly into the YAML report eliminates the need for a manual PR template and allows the information to be automatically extracted for the comparison matrix. During PR submission of an implementation, automated CI checks or reviewers can then easily verify the YAML report for this required metadata before merging.

[skitt]

This makes sense, thanks!

In today’s SIG call we discussed whether to require these flags when producing the YAML report, but decided to leave them optional so that users can integrate the YAML report into test automation without having to fill in all the fields.

[skitt]

/assign @AnupamGhosh