[FEATURE] Decomposition of key functionalities into libraries

Feature Description

Operations performed by stackql are to be implemented through client agnostic libraries. This includes functionality such as:

• CRUD functionality against resources:
  • openapi3 / http based.
  • External SQL data sources.
  • Calls against golang or C software libraries.
  • [Possible architecture] VM implementation for all of these, plus sync and recovery primitives.
• Auth flows of various types.
• Transaction support for composed CRUD operations.
• Query analysis / validation.

Initial stages of this effort are in https://github.com/stackql/any-sdk

Strategy here is for useful functionality which is key to stackql to be available for other tooling in a language- and platform-agnostic manner.

Example(s)
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Possible Approaches or Libraries to Consider
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Start by reviewing the initial work in the linked stackql/any-sdk repository and compare it with stackql's listed responsibilities: CRUD, authentication, transactions, and query analysis. The issue names no files, tests, entry points, or acceptance criteria, so the scope and definition of done need to be established before implementation.