Jira tasks return no outputs, so a created issue's key and URL can't be used downstream

## Problem

`io.kestra.plugin.jira.issues.Create` creates the issue but returns nothing — its outputs schema is
empty. There is no way for a later task in the same flow to reference the issue that was just
created.

This makes Jira the odd one out among the ticketing plugins:

| Task | Outputs |
|---|---|
| `io.kestra.plugin.github.issues.Create` | `issueNumber`, `issueUrl` |
| `io.kestra.plugin.servicenow.Post` | `result` (the created record) |
| `io.kestra.plugin.jira.issues.Create` | *(nothing)* |

`issues.CreateComment` and `issues.UpdateFields` also return nothing, so the same gap applies to
them.

### Steps to reproduce

```yaml
id: jira_outputs
namespace: company.team

tasks:
- id: create_issue
type: io.kestra.plugin.jira.issues.Create
baseUrl: https://your-domain.atlassian.net
username: your_email@example.com
password: "{{ secret('JIRA_API_TOKEN') }}"
projectKey: OPS
summary: "Something failed"

- id: use_it
type: io.kestra.plugin.core.log.Log
message: "Opened {{ outputs.create_issue.key }}"
```

### Expected behaviour

`create_issue` exposes the created issue, at least its key (e.g. `OPS-123`), its id, and a browsable
URL, so `use_it` can log `Opened OPS-123`.

### Actual behaviour

`outputs.create_issue` is empty and the second task fails to resolve the expression. The issue key is
only visible by opening Jira by hand.

### Why it matters

Anything that has to act on the issue after creating it is currently impossible: commenting on it,
updating it, posting its link to Slack, or recording it against an incident. Jira's own REST response
to the create call already carries the id, key and self link, so the information is available at the
moment it is discarded.

This blocks linking an external ticket to a Kestra EE case
(https://github.com/kestra-io/kestra-ee/issues/10859), where the documented pattern is to create the
ticket and then pass its key and URL to a follow-up task. That pattern is expressible for GitHub
today and not for Jira.