[Notifications] Empty Affected project(s) in JIRA when limit to parent project and Group NEW_VULNERABILITY

### Current Behavior

The `Child` project is not listed in created JIRA ticket in the `Affected project(s)` section when Alert is limited to the `Parent` Project.
Technically it seems that the template field `subject.affectedProjects` is empty, however, it is filled correctly when
`Limit to projects` is removed from JIRA alert configuration.

### Steps to Reproduce

1. Create a `Parent` project
2. Create Jira Alert with:
* `Publisher` set to `Jira`
* `Scope` set to `PORTFOLIO`
* `Group` set to `NEW_VULNERABILITY`
* `limit to`->`Limit to projects` set to `Parent` project
* `Notification Level` set to `INFORMATIONAL`
* Configure `Destination` and `Jira ticket type`


3. Create a `Child` project which is a child of `Parent` project
4. Upload sbom(With vulnerability) to `Child` project
5. Observe that created ticket in JIRA has an empty section `Affected project(s)` in the description


### Expected Behavior

Created Ticket in JIRA should contain the `Child` project in the `Affected project(s)` section in the description.

### Dependency-Track Version

4.8.2

### Dependency-Track Distribution

Container Image

### Database Server

PostgreSQL

### Database Server Version

11.13.0

### Browser

Other

### Checklist

- [X] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [X] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported