add stream_logs parameter to trigger_sync

[zzstoatzz]

Summary

This PR includes exposes a stream_logs parameter to the trigger_sync task to surface airbyte sync logs through the Prefect logger and adds associated tests / fixtures.

This required refactoring AirbyteClient.get_job_status to conditionally return logs if stream_output is True.

This PR also switches from the standard python logger to the logger fetched by get_run_logger(), which required a change to all associated unit tests that previously called the Task.fn() method.

Relevant Issue(s)

addresses #19

Checklist

• Summarized PR's changes in CHANGELOG.md

[ahuang11]

Looks nice! Can you share a screenshot/code snippet of what the output looks like?

[zzstoatzz]

Sample output when stream_logs=True (logged at INFO level among trigger_sync task logs

2022-09-17 22:20:40 �[32mINFO�[m i.a.w.w.WorkerRun(call):49 - Executing worker wrapper. Airbyte version: 0.38.3-alpha
2022-09-17 22:20:40 �[32mINFO�[m i.a.w.t.TemporalAttemptExecution(get):108 - Docker volume job log path: /tmp/workspace/20534/0/logs.log
2022-09-17 22:20:40 �[32mINFO�[m i.a.w.t.TemporalAttemptExecution(get):113 - Executing worker wrapper. Airbyte version: 0.38.3-alpha

...

{"type":"string"},"Individual Filling out This Form":{"type":"string"},"Total of Each Fuel Transfer by Equipment":{"type":"string"}}},supportedSyncModes=[full_refresh],sourceDefinedCursor=<null>,defaultCursorField=[],sourceDefinedPrimaryKey=[],namespace=<null>,additionalProperties={}],syncMode=full_refresh,cursorField=[],destinationSyncMode=overwrite,primaryKey=[],additionalProperties={}]],additionalProperties={}],failures=[]]
2022-09-17 22:20:50 �[32mINFO�[m i.a.w.t.TemporalUtils(withBackgroundHeartbeat):236 - Stopping temporal heartbeating...

[ahuang11]

Thanks for addressing the comments! Was wondering if this is ready for another review?

[desertaxle]

I like the direction that these changes takes us, but unfortunately there are some breaking changes. In order to support this I think we'll need to deprecate the current tasks and create a new ones to give users a smooth transition. The old tasks can emit a DeprecationWarning and guide users to use the new tasks/flows. This will also be a good chance to introduce a block, since that might lead to some breaking changes as well.

Let me know if there's any part of this that you'd like to discuss and/or pair on!