appview doesn't handle moderation correctly.

[itaru2622]

Describe the bug

related to https://github.com/bluesky-social/atproto/discussions/2511

when using the appview based on this repository code, the appview's label table is always empty even ozone publishes events to com.atproto.label.subscribeLabels. as the results, moderation cannot work and users have to see undesired posts in the case.

To Reproduce

Steps to reproduce the behavior:

# for minimum
1. deploy  appview based on this repository code (DO NOT USE OFFICIALLY HOSTED APPVIEW).
2. assign label to any post on ozone as usual
3. check the appview's label table. it is always empty regardless ozone/labeler's activity. 

you can use https://github.com/itaru2622/bluesky-selfhost-env to deploy bluesky components for this test.

Expected behavior

Details

open source appview can also handle moderation like officially hosted appview can. i.e appview labe; table should be updated according to the ozone/labeler's activity, even open source based appview.

• Operating system: debian12 for docker host
• Node version: depends docker images
  • 20 for https://github.com/bluesky-social/atproto/blob/main/services/bsky/Dockerfile
  • 18 for https://github.com/bluesky-social/social-app/blob/main/Dockerfile

Additional context

[itaru2622]

I made below workaround tool and find it gets expected results. https://github.com/itaru2622/bluesky-selfhost-env/blob/master/ops-helper/apiImpl/subscribeLabels2BskyDB.ts

the above tool requires endpoint of ozone service on starting. so it needs to detect new labeler joining to the network in real case.

that matter is described in https://github.com/bluesky-social/atproto/discussions/2571