Chore: Update Poe tasks to be more DRY

_Originally posted by @aaronsteers in https://github.com/airbytehq/airbyte/pull/62525#discussion_r2305998148_

> @dbgold17 - I would like to make this more DRY but I'm not confident as of now that I have the syntax correct to do so. Specifically, the nuance is whether `poe task arg1 arg2` will get correctly passed with two args, or if `"arg1 arg2" will get injected a single `arg1` arg when one task envolopes another.
>
> I'd like to defer refactor / DRYification until post-merge because this is relatively low pri right now, and I don't have much time to test thoroughly in the multiple invocation scenarios.

>