Feature Request: TM1py / linti integration

[onefloid]

✨Feature Request

🧑‍💻 User Story

As a TM1 developer, I want TI processes on a live TM1 server to be lintable using TM1py, so that I can validate processes without first exporting them to files — regardless of whether that integration is driven from linti or from TM1py.

📝 Description

It's not yet decided which direction the integration should go:

• TM1py as a provider inside linti — linti depends on TM1py and gains a new ProcessProvider (alongside the existing file/YAML providers) that reads/writes processes from a live server.
• linti as a dependency inside TM1py — TM1py-based scripts/pipelines call into linti to lint a process object they already have, without linti needing to know about TM1py's connection details at all.

To keep both options open, the integration should be designed as a clean boundary between "how a process's code is obtained" and "how that code gets linted," rather than coupling the two together for one specific direction.

✅ Acceptance Criteria

• A TI process living only on a TM1 server (no file export) can be linted, using either linti or TM1py as the entry point
• The same set of rules and issue output applies, no matter which side initiates the linting
• Connection/auth problems when talking to the TM1 server produce clear, understandable messages
• Auto-fix results can optionally be written back to the server
• The chosen approach doesn't lock out the other direction later (e.g. no integration detail hard-codes which package owns the connection)