feat: Animate Meshery architecture diagram and add section

[shteypandey28-hue]

Description

This PR improves the pull request template by enhancing clarity, formatting, and contributor guidance. The updated template helps contributors provide more structured information, making reviews faster and more efficient.

Changes Included

• Refined PR description structure
• Improved readability and formatting
• Added clearer instructions for reviewers and contributors
• Maintained DCO/sign-off reminder for signed commits

Notes for Reviewers

• Verify formatting and wording consistency
• Ensure all contribution guidelines remain accurate

Related Issue

Fixes #

Signed commits

• Yes, I signed my commits.

[github-actions]

🚀 Preview deployment: https://layer5.io/pr-preview/pr-7715/

Note: Preview may take a moment (GitHub Pages deployment in progress). Please wait and refresh. Track deployment here

[shteypandey28-hue]

Kindly review it . @saurabhraghuvanshii

[Rajesh-Nagarajan-11]

@shteypandey28-hue Add a recorded video of the output please.

[shteypandey28-hue]

Meshery.animation.mp4

Hi @Rajesh-Nagarajan-11

Thanks for the review! I've attached a recorded video of the animated architecture diagram in action below.

I've also optimized the implementation—the CSS keyframe animations are now embedded directly within the native SVG <style> block and loaded via a lightweight tag. This approach provides super smooth animations and hover interactions while entirely avoiding the SVGR out-of-memory build issues we were seeing during CI deployments.

Everything is building successfully and rendering great! Let me know if you need anything else, otherwise this should be ready to merge.

[saurabhraghuvanshii]

@shteypandey28-hue What is use of this??

[shteypandey28-hue]

Same as below — this was an accidental commit of GitHub Actions workflow run data. It's been removed now. Sorry for the noise!

[saurabhraghuvanshii]

@shteypandey28-hue what is purpose of this file? I'm not seeing any import of this.

[shteypandey28-hue]

Apologies, this was accidentally committed — it's a GitHub API response that got staged by mistake. I've removed it in the latest push. Thanks for catching it!