docs: add documentation for the refinement process in the contribute guide

[YashPimple]

Description

This pull request addresses the issue #2675, where the goal is to document the refinement process in the contribute guide.

Fixes #2675

Changes Made:

• Added a new page named refinement-guide.md in the contribute/general section.
• Updated the contribut-guidelines-gen.md file to include guidance on creating and refining tickets for proposed work.
• Provided detailed for contributors and members on how to participate in refinement meetings and improve their contributions iteratively.

Checks

• My PR fulfills the Definition of Done of the corresponding issue and not more (or parts if the issue is separated
  into multiple PRs)
• I used descriptive commit messages to help reviewers understand my thought process
• I signed off all my commits according to the Developer Certificate of Origin (DCO)(
  see Contribution Guide)
• My PR title is formatted according to the semantic PR conventions described in
  the Contribution Guide
• My content follows the style guidelines of this project (YAMLLint, markdown-lint)
• I regenerated the auto-generated docs for Helm and the CRD documentation (if applicable)
• I have performed a self-review of my content including grammar and typo errors and also checked the rendered page
  from the Netlify deploy preview
• My changes result in all-green PR checks (first-time contributors need to ask a maintainer to approve their test runs)

[StackScribe]

You need to resolve the spell-check errors. This is documented in an unmerged PR: #2504

[StackScribe]

The readthedocs preview just shows a very brief bullet list but omits a lot of what you've written. Does all the text render when you build.it locally?

[odubajDT]

Hi @YashPimple any updates on this PR? Do you need support ?

[YashPimple]

Hi @YashPimple any updates on this PR? Do you need support ?

Heo @odubajDT Thanks for checking in i have made the suggested changes please do have alook

[YashPimple]

en you build.it locally?

Hello @StackScribe the text get rendered but it does show us the output in General information about contributing section but if we search the content namedrefinement timeblock in the search box above then we are able to view the changes.

[mowies]

@YashPimple if you want the pages to show up, you need to add them to the nav: section in mkdocs.yml in the root of the repo :)

[YashPimple]

@YashPimple if you want the pages to show up, you need to add them to the nav: section in mkdocs.yml in the root of the repo :)

Oo

@YashPimple if you want the pages to show up, you need to add them to the nav: section in mkdocs.yml in the root of the repo :)

[mowies]

this is great so far! I left some comments with improvements :)

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[YashPimple]

this is great so far! I left some comments with improvements :)

@mowies incorporated the suggested the improvements🫡

[mowies]

LGTM!

[mowies]

thanks for this @YashPimple , great work!