feat(boardsv2): initialize reposting

[x1unix]

See the original issue

Closes: #3227

[Gno2D2]

🛠 PR Checks Summary

🔴 Maintainers must be able to edit this pull request (more info)

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check) (checked by @jeronimoalbi)
• The pull request description provides enough details

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🔴 Maintainers must be able to edit this pull request (more info)

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 The pull request was created from a fork (head branch repo: gnostudio/gno)

Then

🔴 Requirement not satisfied
└── 🔴 Maintainer can modify this pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

The pull request description provides enough details

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 Not (🔴 Pull request author is a member of the team: core-contributors)
    └── 🟢 Not (🔴 Pull request author is user: dependabot[bot])

Can be checked by

• team core-contributors

[x1unix]

@jeronimoalbi can you please take a look 🙏

[jeronimoalbi]

	// TODO: figure out a way to decouple posts from a global storage.

I'm thinking we should eventually decouple it by having the render functions implemented as realm functions instead of Post methods, otherwise repostBoardID should instead be repostBoard being of type *Board.

cc @salmad3

[jeronimoalbi]

This would be a separate issue.

[jeronimoalbi]

@x1unix when I tried reposting locally I noticed the repost helper link doesn't assign the threadID to the input field. You can see that by clicking on the [repost] link.

[jeronimoalbi]

A couple of things to consider.

1. The rendered repost Markdown could be improved, we could use the layout that other platforms use for reposts as inspiration for a layout that makes more sense.

2. I think the details being displayed after the body should refer to the repost instead of the source post. For example the [x] delete link would delete the source post instead of the repost.

3. We have to consider the repost as the main post in this context, where the source post is treated just as content (body) of the repost, being the repost the clickable title.
   Right now clicking will take users to the source post so at the moment is not possible to add comments for the repost.

4. We should support reposting comments. We could implement it in a different issue. We could even maybe consider to implement it after the MVP if it makes sense, assuming we are good to go with only supporting reposting thread initially (cc @salmad3).

[x1unix]

@jeronimoalbi moving this to #3513 as GitHub borked the branch during merge update from a GUI