feat: add organizer dashboard

[kittybest]

Update
Keep this as a separate branch (not merging this), wanna integrate registry stuff on the dev branch and merge it to main first.

Description

• update Navbar tags displayed
• add /admin page for organizer dashboard
• add a temporarily RoundContext for managing the organizer dashboard global UI state
• UI for deploy contracts
• UI for deploy rounds
• UI for display rounds
• the round info are displayed correctly
• dark mode for the above UI
• rearrange pages hierarchy
• make duplicate components be reusable ui components (such as submit button section, form section, etc.)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
maci-platform	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 2, 2024 4:03pm

[0xmad]

@kittybest thanks, there are some comments and why PR is for dev branch?
maci-platform repo has main branch as current changes and tags for stable versions.

[0xmad]

Don't use arrow functions inside jsx

[kittybest]

then should we also change the one inside features/applications/components/ApplicationForm.tsx?

[0xmad]

If you see it's used somewhere, it's better to change it because it affects performance.

[kittybest]

@kittybest thanks, there are some comments and why PR is for dev branch? maci-platform repo has main branch as current changes and tags for stable versions.

maybe we should find a better name for it? or are you saying why merge this to dev instead of main? because before was thinking about integrating multi-round and fetching data from subgraph and registry contract on the dev, but now since the registry and other packages are ready, could change the base to main

since currently the only the dev branch containing the multi-round display logic, this branch is based on the multi-round interface. So if we wanna change the branch to be merged to main branch, we need to merge the current dev to main first. How do you think?

[0xmad]

@kittybest thanks, there are some comments and why PR is for dev branch? maci-platform repo has main branch as current changes and tags for stable versions.

maybe we should find a better name for it? or are you saying why merge this to dev instead of main? because before was thinking about integrating multi-round and fetching data from subgraph and registry contract on the dev, but now since the registry and other packages are ready, could change the base to main

since currently the only the dev branch containing the multi-round display logic, this branch is based on the multi-round interface. So if we wanna change the branch to be merged to main branch, we need to merge the current dev to main first. How do you think?

I think let's keep dev for now as we discussed before. When we get rid of mock data and integrate new logic with the ui, we can merge dev into main.