Updates to fod sast-scan setup to keep existing settings

[kadraman]

Minor updates the fod sast-scan setup command so that "aviator" and "oss" settings are not overwritten when they are not supplied. In order to remain backwards compatible existing -use-aviator and --oss have been kept and been made "negatable" so that --no-use-aviator and --no-oss are also available.

Tidied up and hardened technology stack/language level based on Copilot suggestions.

[Copilot]

Pull request overview

This PR updates the FoD SAST scan setup command to preserve existing OSS (Open Source Analysis) and Aviator settings when not explicitly specified, improving the command's behavior to avoid overwriting previously configured settings.

Key changes:

• Made --oss and --use-aviator options negatable (auto-generating --no-oss and --no-aviator flags)
• Added logic to fallback to existing setup values when these options are not provided
• Added @JsonInclude(NON_NULL) to the request class to exclude null fields from API calls

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.

File	Description
FoDScanConfigSastSetupRequest.java	Added @JsonInclude(NON_NULL) annotation to prevent null values from being sent in API requests
FoDScanConfigSastDescriptor.java	Added includeFortifyAviator field to capture existing Aviator setting from API responses
FoDSastScanSetupCommand.java	Updated option declarations to be negatable; added fallback logic to preserve existing OSS and Aviator settings; improved technology stack ID parsing with better error handling

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

Comments suppressed due to low confidence (1)

fcli-core/fcli-fod/src/main/java/com/fortify/cli/fod/sast_scan/cli/cmd/FoDSastScanSetupCommand.java:169

• Potential uncaught 'java.lang.NumberFormatException'.

                    return Integer.valueOf(lookupDescriptor.getValue());