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 new options --no-aviator and -no-oss added to explicitly remove these settings.

[Copilot]

Pull request overview

This PR updates the fod sast-scan setup command to preserve existing "aviator" and "oss" scan settings when they are not explicitly provided by the user. To support this, new --no-aviator and --no-oss options have been added to allow explicit removal of these settings while maintaining backward compatibility with the existing --use-aviator and --oss options.

Key changes:

• Added conditional logic to preserve existing OSS and Aviator settings from current scan configuration when not explicitly specified
• Introduced mutual exclusivity validation to prevent conflicting option combinations (e.g., --oss and --no-oss together)
• Applied @JsonInclude(JsonInclude.Include.NON_NULL) to request objects to omit null fields from API requests

Reviewed changes

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

File	Description
FoDMessages.properties	Added descriptive messages for new --no-oss and --no-aviator command options
FoDScanConfigSastSetupRequest.java	Added @JsonInclude annotation to exclude null fields from JSON serialization, enabling preservation of unspecified settings
FoDScanConfigSastDescriptor.java	Added includeFortifyAviator field to descriptor to capture existing Aviator setting from API responses
FoDSastScanSetupCommand.java	Implemented main logic: removed default values from option fields, added new negative options, implemented mutual exclusivity checks, and added priority-based logic to preserve or override OSS/Aviator settings based on user input