CID-3159: Use yaml as manifest extension

[kostas-petrakis]

• Instead of yml use yaml as the officially supported manifest extension

🛠 Changes made

The manifest file extension should be yaml instead of yml

✨ Type of change

Please delete the options that are not relevant.

• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

🧪 How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

• Change the manifest file extension to yaml, the file should be processed
• Change the manifest file extension to yml, the file should be ignored

🏎 Checklist:

• My code follows the style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• Any dependent changes have been merged and published in downstream modules
• I have made corresponding changes to the documentation (README.md)
• My commit message clearly reflects the changes made
• Assigned the appropriate labels (version, PR type, etc.)

[mohamedlajmileanix]

@kostas-petrakis LGTM, but the building is failing due to detekt error. Try running detekt locally and commit the changes.

[github-actions]

LeanIX GitHub Agent Code Coverage

File	Coverage [100%]	🍏
Constants.kt	100%	🍏

Total Project Coverage	70.91%	🍏

[kostas-petrakis]

Thanks @mohamedlajmileanix did a full build locally passed, rebased and good to go (I think :) )

[mohamedlajmileanix]

Small note, I think if we really want to test that it won't process files with UNSUPPORTED_MANIFEST_EXTENSION, then we need to verify(exactly=0) for a message with the path for the file with UNSUPPORTED_MANIFEST_EXTENSION.

[kostas-petrakis]

Good one, I will extend the tests :)

[kostas-petrakis]

Updated, @mohamedlajmileanix let me know if it looks ok or if there is a better way for the test.