[BUG] Multiple `<env>.bicepparam` creates multiple issues for findings in `main.bicep`

### Existing rule

Azure.AppService.WebSecureFtp

### Description of the issue

This happens with multiple rules, but let's take `Azure.AppService.WebSecureFtp` as an example.

We have a `main.bicep` that creates a `br/public:avm/res/web/site:0.3.5` with `siteConfig: {}` that takes no parameters, so `bicepparam` should not affect this. In other works: All `siteConfig: {}` settings and values are defined inside `main.bicep`.

We then have multiple `.bicepparam`, let's say `test.bicepparam` and `prod.bicepparam`.

Events:

* PSRule code scanning with created one issue per `.bicepparam`.
* We add `siteConfig: {ftpsState: 'FtpsOnly'}` to `main.bicep` and trigger a new PSRule scan.
* Only the issue tied to `prod.bicepparam` gets closed.

### Error messages

None

### Reproduction

See description.

### Version of PSRule

2.9.0

### Version of PSRule for Azure

1.36.0

### Additional context

_No response_