Add workflow file for blackduck scanning

[AAndrisa]

PR Description

This check will be triggered when a push is made on the main branch or a release tag is created.
A blackduck scanning of the project will be made and uploaded on the product page from analogdevices blackduck server.

PR Type

• Bug fix (a change that fixes an issue)
• New feature (a change that adds new functionality)
• Breaking change (a change that affects other repos or cause CIs to fail)

PR Checklist

• I have conducted a self-review of my own code changes
• I have commented new code, particulary complex or unclear areas
• I have checked that I did not intoduced new warnings or errors (CI output)
• I have checked that components that use libiio did not get broken
• I have updated the documentation accordingly (GitHub Pages, READMEs, etc)

[rgetz]

Where is the "product page from analogdevices blackduck server."? Is that something that is publicly accessible?

flagging that there is GPL software in something that is released under GPL seems like a waste of resources.

Building a software BOM, is something else, and may be valuable for those involved, but that should end up in the release artifacts, not just on the blackduck server...

[stephenkilbaneadi]

Where is the "product page from analogdevices blackduck server."? Is that something that is publicly accessible?

I concur. If there's a configuration that relies on internal tooling, that should be configured internally, and not part of the open repo. Conversely, if there's an open configuration, it should be one that is deployable by others (e.g. a configuration that works with OSS Review Toolkit or ScanOSS, etc.).