/v1/names/wowscience.id.stx is not returned by the API

[pradel]

Describe the bug

When accessing https://stacks-node-api.mainnet.stacks.co/v1/names/wowscience.id.stx, the API is not returning the info regarding this username, instead, it's redirecting to https://registrar.stacks.co/v1/names/wowscience.id.stx to show the data included in the registrar.
This would be the expected behavior for a pending subdomain not submitted to the blockchain. However, the tx registering this username was included in an anchor block 10 days ago, see https://explorer.stacks.co/txid/2a0939c461c9caff0a91c5b66d0290dd0d16153f9b3c96edb3cc000e88e77cfc?chain=mainnet. The API should have the info and return it.
The result is that asking the names that SP12YGP1C4V0XRSHDW9G2PSEZRK1T15M66K1GKMBR is holding return an empty array.
The user do not see the username in the Hiro wallet and can't connect to Sigle at the moment.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://stacks-node-api.mainnet.stacks.co/v1/names/wowscience.id.stx
2. See that you are being redirected to https://registrar.stacks.co/v1/names/wowscience.id.stx
3. In the JSON response, get the txid and open it in the stacks explorer to see that the tx was mined

Expected behavior

The API should return the information directly as it's included in a block and not rely on the registrar.

[rafaelcr]

I originally thought this issue was only a bug related to canonical data, however, upon further inspection it looks like in some of our instances we are not receiving an /attachments/new message from the node which contains the updated zonefile we need to process in order to detect this new subdomain.

We're currently investigating whether this is a bug on the API side or the stacks node side.

[rafaelcr]

Blocked by this issue on the Stacks blockchain: stacks-network/stacks-core#3270