💡 Prepare GovTool for Localization

### Area

Other

### Is there new design needed?

Yes

### What?

The GovTool interface needs to be **fully prepared for localization** to support multiple languages. This includes ensuring all UI components are translatable and providing appropriate documentation on how localization files should be used.

The following **GovTool components** must be made localization-ready:
- **Wrapper**
- **Voting Pillar**
- **Delegation Pillar**
- **Proposal Discussion Forum Pillar**
- **Governance Action Outcomes Pillar**

Additionally, the interface should include an **always visible and easily accessible language switcher** for users to change languages seamlessly.

### Why?

- Improves accessibility and inclusivity by allowing users to interact with GovTool in their preferred language.
- Ensures consistency in translated content across all components.
- Provides clear documentation on how localization files should be structured and used.
- Helps maintain proper handling of **user-generated content**, including recommendations and considerations for different languages.

### How?

- Make sure all pillars are following i18n standard and all strings used in the application are part of the translation files
- **Add a language switcher** that is always visible and easy to access.
- **Create GitBook documentation** covering:
- How localization files should be structured and updated.
- Best practices for handling **user-generated content** in different languages.
- Considerations for regional formatting (date, time, currency, etc.).

### (Optional) User Story with acceptance criteria

- [ ] All UI components listed are **fully localization-ready**.
- [ ] A **language switcher** is implemented and easily accessible.
- [ ] Localization system dynamically loads translated content.
- [ ] **GitBook documentation** is created with clear guidance on localization implementation.
- [ ] Considerations and recommendations for **user-generated content** are included.