Add more unique deployment names

Hi - I was wondering if there was some way to customize the "Deployment" or "Pipeline" fields to show more unique information? Or, if an improvement could be made?

Deployments for our team can mean deploying multiple components separately. A frontend, backend, poller/worker service, etc.

In this screenshot you can see that they currently just show "deploy". But, this isn't too useful since I don't know which is which. Once you click the underlying link it will actually take you to the GitHub action, where you can actually determine which belongs to which. It would be nice to map one of these fields to the name of the deploy instead.

[Digging into the code here](https://github.com/atlassian/github-for-jira/blob/6d7d2b35be67d66e696585cbe187844f76da8091/src/transforms/transform-deployment.ts#L266-L278); I suspect this is where they are mapped. `deployment.task` I suspect resolves to the value `deploy` for `displayName`. But, I'm not too sure what to change in my github action, since it doesn't seem we specify that anywhere.

First verify the repository status, since it is marked deprecated and moved to a private repository. Then read src/transforms/transform-deployment.ts around lines 266-278 and trace how deployment.task becomes displayName; done means determining whether a unique component or deployment name can be exposed in the Deployment or Pipeline fields.

Written by the indexing model from the issue text.