ci: only trigger actions for code analysis workflows after testing changes

[juarezr]

This PR has the objective of avoiding double triggering of workflows

Changes

1. only trigger actions for code analysis workflows after testing changes
2. allow manual triggering of code analysis workflows

Checklist

Use this checklist to ensure the quality of pull requests that include new code and/or make changes to existing code.

• Source Code guidelines:
  • Includes unit tests
  • New functions have docstrings with examples that can be run with doctest
  • New functions are included in API docs
  • Docstrings include notes for any changes to API or behavior
  • All changes are documented in docs/changes.rst
• Versioning and history tracking guidelines:
  • Using atomic commits whenever possible
  • Commits are reversible whenever possible
  • There are no incomplete changes in the pull request
  • There is no accidental garbage added to the source code
• Testing guidelines:
  • Tested locally using tox / pytest
  • Rebased to the master branch and tested before sending the PR
  • Automated testing passes (see CI)
  • Unit test coverage has not decreased (see Coveralls)
• [
• State of these changes is:
  • Just a proof of concept
  • Work in progress / Further changes needed
  • Ready to review
  • Ready to merge

[coveralls]

Pull Request Test Coverage Report for Build 8287898034

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 91.072%

---

Totals
Change from base Build 8286826955:	0.0%
Covered Lines:	13352
Relevant Lines:	14661

---

💛 - Coveralls