persist run record for custom actions that produce outputs

[VinozzZ]

What does this change

When a custom action that does not modify bundle resources and is stateless, its run should be recorded in the database if the action produce any outputs.
This PR implements this behavior.

What issue does it fix

Closes #1980

Notes for the reviewer

Checklist

• Did you write tests?
• Did you write documentation?
• Did you change porter.yaml or a storage document record? Update the corresponding schema file.
• If this is your first pull request, please add your name to the bottom of our Contributors list. Thank you for making Porter better! 🙇‍♀️

Reviewer Checklist

• Comment with /azp run test-porter-release if a magefile or build script was modified
• Comment with /azp run porter-integration if it's a non-trivial PR

[carolynvs]

Looks good! The docs just need a few edits and it's ready to go 👍

[carolynvs]

Are you trying to demonstrate that this action will be recorded? It's a bit unclear for this example why you are including an output but then not discussing how actions that generate outputs are recorded.

Maybe split this into two custom actions? Keep myhelp as it was, and then add the getLicense one too, along with a bundle output defined so that you can explain why one is recorded and the other one isn't?

[carolynvs]

Suggested change

	* `stateless`: Indicates that the action is purely informational and can be executed before the install action runs. It also,means that credentials are not required, and that Porter should not keep track of when this action was last executed.
	* `stateless`: Indicates that the action is purely informational and can be executed before the install action runs.

Now that the logic for when a run should be persisted is more complicated, this sentence is confusing since it doesn't address it fully. How about explaining it only once next to the above example? "Porter will record a run when the action modifies resources, is not stateless, or generates an output."