Extract Python components into their own packages

[eabatalov]

The following packages were introduced:

• "indexify-python-utils" with common functionality for components written in Python. Not published to PyPi. It currently includes:
  ** Logging configuration for services written in Python (used by Function Executor and Executor).
  ** HTTP client utils (used by Python SDK and Executor).
  ** Common build and testing scripts for all Python packages.
• "indexify-python-sdk" for Python SDK library. Not published to PyPi.
• "indexify-function-executor" for Function Executor. Not published to PyPi.
• "indexify-executor" for Executor. Not published to PyPi.
• "indexify" (depends on all the 4 packages above ^ and includes the CLI). Published to PyPi. This is the same "all in one" package we were using right now. It should be compatible with all existing customer UX. The idea is that "indexify" package combines all Open Source Indexify components in one package and customers can use the package to develop their workflows and to run local or distributed Indexify clusters using the CLI and also to build their function images.

Also added README.md for all the packages and their tests to clarify what functionality belongs where and how the packages relate to each other.

Versioning:

"indexify-python-sdk" package has the current latest version 0.2.48. "indexify" package has the same current version 0.2.48. All other packages have version 0.1.0 as it's not as important to keep their versions the same as the current 0.2.48.

The versioning policy from now on is the following:

• Versions of all the packages are independent except "indexify" package.
• When a package version gets incremented then "indexify" package version gets incremented too. ** This ensures that all important enough updates in any Indexify component results in user visible version change.

Also update github actions to:

• Work with "indexify" package folder instead of python-sdk package folder.
• Run all the linter checks and tests in all the packages.
• Use poetry version 2.0.0 strictly to prevent random regressions in CI.

And update the lock files with never versions of the dependencies from toml files.

Testing:

make check
make test

Contribution Checklist

• If the python-sdk was changed, please run make fmt in python-sdk/.
• [n/a] If the server was changed, please run make fmt in server/.
• Make sure all PR Checks are passing.