Docs/1530 namespace guide

[Popie52]

Proposed changes

Adds a practical guide for configuring an additional FireFly namespace using the FireFly Helm chart.

The documentation covers:

• Minimal config.extraNamespaces configuration
• Applying the namespace configuration with Helm
• Verifying the namespace through the FireFly API
• Verifying the plugins configured for the namespace
• Using namespace-scoped APIs
• Where to find advanced namespace configuration

The workflow was tested against a local FireFly deployment using the Helm chart.

Fixes #1530

---

Types of changes

• Bug fix
• New feature added
• Documentation Update

---

Please make sure to follow these points

• I have read the contributing guidelines.
• I have performed a self-review of my own code or work.
• I have commented my code, particularly in hard-to-understand areas.
• My changes generates no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• My changes have sufficient code coverage (unit, integration, e2e tests).

---

Screenshots (If Applicable)

---

Other Information

The guide is intentionally focused on the minimal configuration required to add a namespace with the Helm chart, while pointing to the existing namespace and multi-party documentation for more advanced configurations.

The documented workflow was validated locally by deploying the FireFly Helm chart, adding a payments namespace through config.extraNamespaces, and verifying the namespace and its configured plugins through the FireFly API.

[EnriqueL8]

Thanks for this @Popie52 wonder if we couple split it, see below comment and that would enable us to extend it with multiparty config, plugins etc...

[EnriqueL8]

Was expecting this section to be in it's own guide/tutorial type of file. This namespace reference is all about how to configure a namespace. Given this is very specific to the way the helm charts work might be worth splitting this out, what do you think @Popie52 ?

[Popie52]

Agreed on it.
should i keep the focus on basic namespace creation with helm or also cover more advanced configurations like mulltipart and additional pugins?

[EnriqueL8]

Up to you how much time you want to invest in it, we could start off with a basic helm creation in this PR and then a follow up with advanced modes?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.