Create returns no issue URL, so the created issue cannot be linked to

## Problem

`io.kestra.plugin.pylon.issue.Create` outputs `issueId` and the full `issue` object, but no browsable
URL. There is no documented way to link to the issue that was just created — a caller has to know
which field inside the raw `issue` object to dig into, if one is there at all.

Compare the other ticketing plugins, which all expose a URL as a first-class output:

| Task | Outputs |
|---|---|
| `io.kestra.plugin.github.issues.Create` | `issueNumber`, `issueUrl` |
| `io.kestra.plugin.gitlab.issues.Create` | `issueId`, `webUrl` |
| `io.kestra.plugin.zendesk.tickets.Create` | `id`, `url` |
| `io.kestra.plugin.pylon.issue.Create` | `issueId`, `issue` — no URL |

### Expected behaviour

A declared `issueUrl` (or `url`) output pointing at the issue in Pylon, so a later task can log it,
post it to Slack, or record it against an incident without parsing the raw object.

### Actual behaviour

Only the id is addressable. Building a link means hardcoding Pylon's URL shape in the flow, which also
has to account for the US and EU regions the task already distinguishes via `baseUrl`.

### Why it matters

This blocks linking an external ticket to a Kestra EE case
(https://github.com/kestra-io/kestra-ee/issues/10859), where the pattern is to create the ticket and
pass its key and URL to a follow-up task that records it on the case.

Property grouping on this task is in good shape — `apiToken` and `baseUrl` are correctly `connection`,
`title` and `bodyHtml` are `main`. The only oddity is `priority` and `tags` using a `processing` group
that no other plugin uses; harmless, but `advanced` would be more consistent.