feat: implement realm for manual rewards

[harry-hov]

Contains initial implementation for manual reward entry
(as mentioned in 2nd point of #159)

Note:
Please check if moving realm -> r/chess breaks anything

[netlify]

👷 Deploy request for gnochess-signup-form pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	0f83b2d

[netlify]

✅ Deploy Preview for gnochess ready!

Name	Link
🔨 Latest commit	0f83b2d
🔍 Latest deploy log	https://app.netlify.com/sites/gnochess/deploys/65140fa24ef54f0008a8cf2f
😎 Deploy Preview	https://deploy-preview-171--gnochess.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[moul]

i think we should just keep a single 4_deploy_realm rule that uploads as many realm as needed (two at the moment).

[harry-hov]

Yeah. makes sense. Done.

[moul]

if we go with moving realm -> realm/chess; I'd go for r/chess.

[moul]

do we already have an admin address shared with the competition operators? if not we should set it now.

cc @thehowl @zivkovicmilos @albttx

[moul]

It prevents a single address from having multiple entries.

We can survive with this condition, but I think it makes sense for such manual entry realm to support multiple entries per address.

[harry-hov]

I don't think it's a good idea to have multiple entries for single address.

Btw you can always override points (increase/decrease).

For some reason we want entry for every points earner. we can have something like:

// RewardEntry represents a reward entry
type RewardEntry struct {
	address std.Address
        totalPoints uint64
	points  []*Point

	updatedAt time.Time
	updatedBy std.Address
}

type Point struct {
        points  uint64
	reason  string
}

Considering the time constrains, I suggest we shouldn't make things unnecessarily complex, unless it is need of the hour

[moul]

could you add at least one unit test so that gno test runs against the folder and make basic checks like syntax, etc?

I think you can make a simple test adding a few entries and checking the result of Render(); no need to test the whitelisting feature IMO.

[harry-hov]

could you add at least one unit test so that gno test runs against the folder and make basic checks like syntax, etc?

Done @moul.

[albttx]

please rebase and also fix for .github/workflows/deploy-realm.yml

[harry-hov]

Done -> Can you please verify the changes? -> 0f83b2d