Move Farcaster to new app

[rbennettcw]

We can't deploy the app with Farcaster functionality due to the Heroku slug size constraint. The long term solution is Docker, but that'll require some non-trivial changes to the CI/build process.

The short/medium term solution is to move the Farcaster integration to a new app to move the related node dependencies out of the main app.

Acceptance Criteria

• There should be a new app/worker for Farcaster code and related dependencies
• Scripts/docs should be updated to reflect any steps required to run

[rbennettcw]

We've decided to have the FC app make API requests to the main app to query data instead of the FC app accessing the database directly. This will reduce the size and responsibility of the FC app to essentially just serve frames and forward webhook requests to the main app.

Since webhooks are signed via the frames.js library, we may need to add webhooks on the FC app and have them reverse-proxy the payload to the main app– unless there's a smaller library that can handle signing.

[rbennettcw]

Closing since this is no longer needed.