Introducing the home page/mapping feature removes catalogue entries

[BenjoGreeno]

This is a continuation of another thing I raised here regarding scoped oauth - this is some strange behaviour when relying on the API key instead.

Describe the bug
I have one catalogue entry, which has annotations applied allowing for the PagerDuty card to successfully work on the entity page, if I then follow the instructions as per the service entity mapping guide and re-run the backstage service, the catalogue entry I initially used for testing completely disappears.

Below is the log snippet that looks relevant, I've removed the entity ID here and replaced it with [masked-entity-id].

[1] 2024-09-17T10:36:16.099Z rootHttpRouter info [17/Sep/2024:10:36:16 +0000] "GET /api/pagerduty/mapping/entity/component/default/ud.platform.miketestbarebones2006241646 HTTP/1.1" 404 92 "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
[1] 2024-09-17T10:36:16.101Z rootHttpRouter info [17/Sep/2024:10:36:16 +0000] "GET /api/pagerduty/mapping/entity/service/[masked-entity-id] HTTP/1.1" 404 42 "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
[1] 2024-09-17T10:36:16.948Z rootHttpRouter info [17/Sep/2024:10:36:16 +0000] "GET /api/pagerduty/services/[masked-entity-id]?account=*** HTTP/1.1" 200 - "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest

To Reproduce
Steps to reproduce the behavior:

1. I am running this locally, so updating app-config.local.yaml
2. follow the getting started steps here, I am using the API key over scoped (as I can't get that to work currently).
3. I added the following annotations to the entity's catalogue.yaml:

pagerduty.com/account: _our account subdomain here_
pagerduty.com/service-id: _the entity subdomain here_

4. The above results in the PagerDuty card appearing on the entity page
5. Now, follow the steps for the service entity mapping
6. shutdown the server and re-run yarn (simply reloading the page doesn't show the behaviour).

Expected behavior
I should be able to see the entity on the catalogue screen.

Screenshots
Screenshots probably don't help a lot, but this first one highlights the entity I'm talking about with the working card:

I then add the elements to introduce the mapping screen as per the documentation...

if I look for the entity in the PagerDuty mapping page, the entity's pagerduty entry is searchable, however it cannot be mapped to the now missing portal entitiy:

Desktop (please complete the following information):

• MacOS
• Chrome and Firefox

Thanks in advance