docs: change the runbok for appinspect update

[kdoroszko-splunk]

Description

I think it makes more sense to make a fix release each time we update appinspect version. We'd prevent ourselves from rolling out the template each time there is a feat release of appinspect.

Checklist

• README.md has been updated or is not required
• push trigger tests
• manual release test
• automated releases test
• pull request trigger tests
• schedule trigger tests
• workflow errors/warnings reviewed and addressed

Testing done

No tests are needed

[mkolasinski-splunk]

@kdoroszko-splunk Would rollout really be necessary in such case? Wouldn't releasing a patch for reusable workflow with bumped version of appinspect action be enough?
I'm bit worried for automated feat versions updates that may eventually break the workflows.

[kdoroszko-splunk]

@kdoroszko-splunk Would rollout really be necessary in such case? Wouldn't releasing a patch for reusable workflow with bumped version of appinspect action be enough? I'm bit worried for automated feat versions updates that may eventually break the workflows.

I think we're on the same page here: I'd like to always make patch release of reusable workflow when appisnspect is updated.
However, at the moment the documentation says to create a "feat" PR directly to main branch, which per my understanding will create a minor release of reusable workflow (and then the rollout is required).