Migrate from FOSSA to SRS configuration

[skammari-splunk]

Summary

This PR adds a srs.yaml configuration file generated from the existing .fossa.yml configuration.

What Changed

Added srs.yaml with settings migrated from .fossa.yml
Mapped FOSSA paths.exclude to SRS skip-dirs
Mapped FOSSA targets.exclude (type + path) to SRS skip-files

Next Steps

• Review the generated srs.yaml configuration
• Check warning comments for any unsupported features

[breedx-splk]

Do you want to remove the fossa yaml as part of this PR? Should that go away as well?

I'm curious to see what this looks like and if it will impact our workflow.

[laurit]

Scanning compileClasspath may result in false positives e.g. license report may include libraries that aren't really bundled with the agent, same for vulnerabilities. If this turns out to be an issue how can we work around it?

[laurit]

Suggested change

	# SRS configuration file
	# Generated from .fossa.yml
	#
	# WARNING: The following FOSSA features are NOT supported in SRS
	# (only skip-files and skip-dirs are supported for now):
	#
	# - experimental.gradle.configurations-only: ['runtimeClasspath', 'runtime', 'runtimeOnly', 'runtimeOnlyDependenciesMetadata']
	# FOSSA was configured to scan only Gradle configurations: ['runtimeClasspath', 'runtime', 'runtimeOnly', 'runtimeOnlyDependenciesMetadata']
	# SRS does not support Gradle configuration filtering.
	# Only 'compileClasspath', 'runtimeClasspath' configurations will be scanned.
	#