Support multiple runs of the action in the same job

[travislikestocode]

Description

Somewhat naive attempt at allowing the action to run multiple times in the same job. By deleting the plan and log before running octodns-sync, we make the plan file available to later steps. I also added the plan output to the action for more flexibility. The ability to use multiple octodns_refs is not supported. The ref from the first run will be used for any subsequent runs.

Hope this adequately addresses the concerns in the issue. I'm very open to any change suggestions!

Motivation and Context

See #57

How Has This Been Tested?

Created a test workflow which runs the action twice in the same job, and then prints the plan output. The action run was successful

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have read the CONTRIBUTING document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• [N/A] All new and existing tests passed.

[solvaholic]

I dig it, thank you @travislikestocode! 🙇

The net effect of these changes is a) subsequent workflow job steps using solvaholic/octodns-sync now run instead of failing and b) the plan output exists. I don't see how this can break current use of main so I'm happy to merge them.

I'll kick the linter, see if I can get it to sort itself out...

[solvaholic]

I'll kick the linter, see if I can get it to sort itself out...

Worked around this initially by pushing refs/pull/66/head as the issue66 branch, then updated the linter workflow in #68.