Bug Report: release-bundle-search ignores --url flag and fails with "platform URL is mandatory for lifecycle commands"

Describe the bug

Description

When running release-bundle-search versions (or release-bundle-search names) with the --url flag explicitly provided, the command fails with the following error instead of returning the expected JSON response:

Trace ID for JFrog Platform logs: 1c35005c3fb04334
platform URL is mandatory for lifecycle commands

This suggests the --url flag is not being recognized or applied for release-bundle-search subcommands.
The same behavior is observed with release-bundle-search names.

Current behavior

The release-bundle-search command fails with the following error instead of returning the expected JSON response.

Reproduction steps

Steps to Reproduce

Run the following command:

CI=true jf release-bundle-search versions my-release-bundle-name \
    --access-token="${MY_ACCESS_TOKEN}" \
    --url="https://my-jfrog-platform-url" \
    --project=my-project-key \
    --format=json

Expected behavior

The command returns som JSON format data.

JFrog CLI version

2.99.0

Operating system type and version

macOS Tahoe 26.4.1

JFrog Artifactory version

7.147

JFrog Xray version

?

Start by locating the Go command implementation and flag handling for the release-bundle-search versions and names subcommands, then reproduce the supplied command with --url. Done means both subcommands recognize the platform URL and return the expected JSON response instead of the mandatory-URL error; the payload names no files or tests.