Add governed Ollama local chat client

[CleanDev-Fix]

Summary

• adds TealOllama, a governed client for Ollama's OpenAI-compatible local endpoint
• exports a tree-shakable tealtiger/providers/ollama entrypoint
• adds a no-network Jest test proving TealEngine policy evaluation and TealAudit wrapping around a mocked Ollama chat call
• adds a small local chat example for http://localhost:11434/v1

Changes

• TealOllama extends TealBaseClient so local chat calls go through the existing TealEngine, guard, circuit, monitor, and audit pipeline
• defaults to http://localhost:11434/v1 and supports optional API keys for secured local proxies
• uses tool: "ollama.chat" and action: "ollama.chat.create" so policies can govern local Ollama separately from cloud chat providers
• adds package export and Rollup provider bundle config for ./providers/ollama
• repairs a current TealEngine constructor syntax issue that blocked TypeScript/Jest on main
• adds the package-lock.json required by the existing CI workflow and updates dev tooling ranges so npm audit --audit-level=moderate passes
• fixes the ESLint config preset names so lint can run; full repo lint still reports existing project-wide lint debt outside this Ollama patch

Testing

• npm test -- --runTestsByPath src/client/__tests__/ollama.test.ts
• npm run build:tsc
• npm run build:rollup
• npm audit --audit-level=moderate
• npx eslint src/client/ollama.ts src/providers/ollama.ts

Known existing issue: npm run lint now starts correctly but reports broad pre-existing lint debt across the SDK. The new Ollama runtime files lint cleanly.

Related: agentguard-ai/tealtiger#319

[nagasatish007]

@CleanDev-Fix Merge conflicts from the v1.4.0 release that landed on main today. Can you rebase onto latest main and force-push? I'll squash-merge once it's green.