fix(lifecycle.go): validate params after pulling bundle from tag

[vdice]

What does this change

• Runs parameter validation after pulling a bundle from a tag. In this scenario, the manifest referenced in memory for parameter validation (especially regards those of type file) will only be populated after the bundle is pulled.

Proposed fix for #1320

What issue does it fix

Closes #1320

Notes for the reviewer

Not sure if this is an ideal approach to solving the issue mentioned in #1320 . Other thoughts/ideas?

Checklist

• Unit Integration Tests
• Documentation
• Schema (porter.yaml)

If this is your first pull request, please add your name to the bottom of our Contributors list. Thank you for making Porter better! 🙇‍♀️

[carolynvs]

You nerd sniped me into thinking about a larger solution. 😂 I took your unit test and built on top of it here: #1337

[vdice]

🎉 The more holistic changes in #1337 definitely are preferred over the bandaid fix presented here. Closing this PR.