Add `JobBlock` implementation recipe

[zzstoatzz]

Description

What's cooking? If this PR references an issue, please attach to the existing issue.

Type of change

• [ ] New feature (non-breaking change which adds functionality)
• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

New Recipe Checklist

• [ ] My PR is in the format of Add <project-name> recipe
• [ ] My recipe is reproducible and explains everything needed to run successfully. If my code has external dependencies, I make mention of them.
• [ ] My code is easily understandable and/or well-commented.
• [ ] If my recipe requires a new category (e.g. creating a monitoring/ folder in devops/), I have encapsulated my project within its own subfolder so that others can add their own recipes as well.
• [ ] If my recipe uses Prefect < 2.0, my code is within the prefect-v1-legacy/ folder.

[ahuang11]

I'm personally not a big fan of Foo/Bar examples because they don't really mean anything and they're not relatable (to me anyways). Here's a blog post I randomly found: https://www.techyourchance.com/never-use-foo-bar-baz/

I prefer if this recipe was based off a real life scenario; perhaps a stripped down version of ShellJob (just subprocess.run and subprocess.communicate without the async stuff)?

[zzstoatzz]

Fair point about Foo being non-realistic, I guess I just didn't want to step on the toes of any real collections / blocks that we're writing and confuse anyone

just wanted to put this out here so we could start talking about what should be here