Feature Request: Configurable Ollama Base URL

## 🛠️ Feature Request: Configurable Ollama Base URL
Team 150
### Problem Statement
The current implementation has Ollama's base URL hardcoded to `http://localhost:11434`. This limits flexibility, especially for users who want to point to a self-hosted or remote Ollama instance rather than the default local setup.

### Proposed Solution
Add an `ollama-url` input parameter to the GitHub Action configuration (`action.yml`). This parameter should allow users to specify a custom Ollama server URL. The action should use this input to determine the base URL for connecting to Ollama.

### Acceptance Criteria
- [ ] Introduce a new `ollama-url` input in `action.yml` (with a suitable default if omitted).
- [ ] Update code to use the specified `ollama-url` for all Ollama API calls.
- [ ] Update documentation and `README.md` to explain how to set a custom Ollama URL.
- [ ] Add input validation and error handling for malformed or unreachable URLs.

### Context / Motivation
Making Ollama's base URL configurable enables broader support for diverse CI/CD or on-premise deployments where the Ollama server may not be running on localhost.

### Additional Notes
- Ensure the default (`http://localhost:11434`) is maintained for users who do not specify a value.
- Example usage in workflow:
```yaml
with:
ollama-url: "http://my-ollama-server:11434"
```

Inspect action.yml and README.md first, then locate the Ollama API call sites in the Go code. Add the configurable input while preserving the localhost default, validate malformed or unreachable URLs, and document the workflow usage. Done means all Ollama calls use the selected URL and the relevant tests or checks pass.

Written by the indexing model from the issue text.