Fix: Comparison can be timezone aware

[eco-JoshuaJackson]

Why do we need this change?

Depending on the setup and return from github, the date/time can be timezone aware. This leads to an error TypeError: can't compare offset-naive and offset-aware datetimes that prevents updating repo's appropriately.

What effects does this change have?

• Linting changes
• Ensure that comparison will work for timezone and non timezone aware datetime returned from github
• switch to safe_load for yaml
• fix unescaped logging line that was breaking various linters
• Fixes Timezone aware datetime not being handled approriately #9

[eco-JoshuaJackson]

@cunla Just want to make sure that you saw the bug and this pr and please let me know if you have any questions about it, or if there's any adjustments needed.

[cunla]

@cunla Just want to make sure that you saw the bug and this pr and please let me know if you have any questions about it, or if there's any adjustments needed.

I will look into it later this month

[cunla]

Hi, do you mind removing the linter changes? I think we use different settings and it causes a lot of "noise" here.

[eco-JoshuaJackson]

Hi, do you mind removing the linter changes? I think we use different settings and it causes a lot of "noise" here.

In which case I would suggest publishing the linter configurations that you leverage as part of the repo be it the settings for black, ruff etc so that it remains consistent to the standards you want.

But I've updated to be the bare minimal of changes now so it should be easier to review.

Also of note oddly enough for a design that's meant to update steps to the latest, the steps in this repo could use an update as well.