feat(python): Adding support for pre-commit linter and formatter based on ruff

[kirgrim]

Checklist (if applicable):

• PR title is following https://www.conventionalcommits.org/en/v1.0.0/
• Tested (manually, unit tested, etc.)
• Docs updated (updated docs or a docs bug required)

[kirgrim]

@yesudeep @Irillit I will temporarily disable linter checks in gh actions, as it will require much refactoring which is related to #1820 and more

[yesudeep]

We already have pre-commit checks in captainhook.json. Can you please use that? I don't want us to use 2 different sets of commands because some of us are working on both go and python. These pre-commit checks already exist?

Please edit this file: https://github.com/firebase/genkit/blob/main/py/captainhook.json for the changes

[yesudeep]

@yesudeep @Irillit I will temporarily disable linter checks in gh actions, as it will require much refactoring which is related to #1820 and more

Sounds good

[yesudeep]

Please edit https://github.com/firebase/genkit/blob/main/py/captainhook.json and https://github.com/firebase/genkit/blob/main/py/bin/fmt#L36 as required. They are already managing formatting, pre-commits, pre-pushes, etc.

[kirgrim]

Please edit https://github.com/firebase/genkit/blob/main/py/captainhook.json and https://github.com/firebase/genkit/blob/main/py/bin/fmt#L36 as required. They are already managing formatting, pre-commits, pre-pushes, etc.

I dont really like using captainhook and fmt for these purposes for several reasons:

1. it requires 'golang' depedency which couples our pythonic solution with golang dependencies which i believe is non-optimal
2. pre-commit is a native and commonly accepted solution for linting and formatting which is familiar for most of python devs
3. creating a separate script for formatting and separate for linter definitions is redundant when we could have everything in one place nicely structured, supported and up-to-date

@Irillit @timere-nemo what do you think of it?

[Irillit]

Please edit https://github.com/firebase/genkit/blob/main/py/captainhook.json and https://github.com/firebase/genkit/blob/main/py/bin/fmt#L36 as required. They are already managing formatting, pre-commits, pre-pushes, etc.

I dont really like using captainhook and fmt for these purposes for several reasons:

1. it requires 'golang' depedency which couples our pythonic solution with golang dependencies which i believe is non-optimal

2. pre-commit is a native and commonly accepted solution for linting and formatting which is familiar for most of python devs

3. creating a separate script for formatting and separate for linter definitions is redundant when we could have everything in one place nicely structured, supported and up-to-date

@Irillit @timere-nemo what do you think of it?

I would like to have less dependencies and proceed with pre-commit.

[yesudeep]

I understand Python devs prefer pre-commit just like JS devs prefer husky and Go devs may have their own.
We have cross-runtime unit tests and code generation going on, I'd prefer not to have to maintain multiple commit managers since these bits need to run on the same machine while working on any of these runtimes and some of us work on multiple runtimes (I am working on both Go and Python).

For example, if I'm editing https://github.com/firebase/genkit/blob/main/tests/specs/reflection_api.yaml and fix only the JS affected while leaving the Python broken, my code changes would be incomplete.

Please keep your hooks in captainhook.json for now. We should focus on some more important tasks at the moment.

[kirgrim]

@yesudeep @Irillit I will temporarily disable linter checks in gh actions, as it will require much refactoring which is related to #1820 and more

Sounds good

I did formatting/linting updates in this PR in-place so uncommented that back

[Irillit]

Looks good to me.