Code Conundrum Resolved: New Fix Transforms 'Unfollow' into 'Follow' in Farcaster Example!

Essential bug fix in the hub-nodejs package empowers developers to navigate 'write-data' with ease, abolishing confusion and paving the way for seamless integration!

Commit Details:

fix(example): fix the argument for makeLinkRemove when removing a follow (#2196) ## Why is this change needed? The change is a bug fix in the example code `write-data` in the `hub-nodejs` package (packages/hub-nodejs/examples/write-data). When I was trying to use this package, I was stuck with the original code for a while and finally found it our by checking the source code. So I think the change is needed because it can benefit others (especially new developers) who want to build on Farcaster instead of getting stuck. You can see here too that the test code for `packages/core/src/builders.ts` https://github.com/farcasterxyz/hub-monorepo/blob/76ad1ac2a2d2b219b204239c1e8ccdffc3e309b2/packages/core/src/builders.test.ts#L362 is taking `'follow'` instead of `'unfollow'` ## Merge Checklist _Choose all relevant options below by adding an `x` now or at any time before submitting for review_ - [x] PR title adheres to the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) standard - [x] PR has a [changeset](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#35-adding-changesets) - [ ] PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore) - [ ] PR includes [documentation](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#32-writing-docs) if necessary. <!-- start pr-codex --> --- ## PR-Codex overview The focus of this PR is to correct the type of message being created when removing a follow in the `write-data` example. ### Detailed summary - Updated the type of message from "unfollow" to "follow" when removing a follow in the `write-data` example. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->