Adding security label and Integration Kanban project to PRs

[jana-selva]

Fixes #874

Checklist

Note: If any of the items in the checklist are not relevant to your PR, just check the box.

For any Pull Request

Is the following correct:

• the title of the Pull Request?
• the title of the corresponding issue?
• there are no other open Pull Requests for the same update/change?
• that the issue which this Pull Request fixes ("Fixes...") is mentioned?

When Changes Were Made

Did you:

• update the changelog?
• update the cookiecutter-template?
• update the implementation?
• check coverage and add tests: unit tests and, if relevant, integration tests?
• update the User Guide & other documentation?
• resolve any failing CI criteria (incl. Sonar quality gate)?

When Preparing a Release

Have you:

• thought about version number (major, minor, patch)?
• checked Exasol packages for updates and resolved open vulnerabilities, if easily possible?

[ArBridgeman]

@jana-selva Before merging this, we can test is already to see if it works. You can modify the dependency-update.yml to also work on a branch (so removing the Fail if not running on the default branch), introduce a vulnerability in the branch, and trigger the dependency-update workflow manually in the 'Actions'.

We would hope that the PR is created as desired. If there are issues, then it might indicate other changes are needed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud