Feat: Add components for User-Case-study

[ArafatAbdussalam]

• Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

New Feature for User Case Studies

This PR is related to #347

When a developer tool is said to have great developer experience, what it means is that the time-to-value measure is shorter, easily accessible and enjoyable. A user case study is a detailed description of challenges and solutions faced by developers using the tools. It serves as a guide for other developers and communicates, seamlessly that users can learn how other users implement KubeEdge in their workflow.

• What is the current behavior? (You can also link to an open issue here)

Presently, the KubeEdge website has no section dedicated to user case studies.

• What is the new behavior (if this is a feature change)?

Having a user case study section on the website enables smoother developer experience and saves other costs by KubeEdge. Users are also allowed to tell their stories by sending a message to the KubeEdge Developer Relations team. The new feature added enables the following:

• Search Feature: search by industry tags and search by texts
• Available Case Studies sought by the KubeEdge team
• Direct message or story telling to the team which allows users talk about the challenges, description, solution, impacts, and conclusion
• Enjoyable User Interfaces which enables the users want to explore the website for a longer time

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
  No changes are needed from the users' end points

• Other information:

[kubeedge-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign kevin-wangzefeng after the PR has been reviewed.
You can assign the PR to them by writing /assign @kevin-wangzefeng in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubeedge-bot]

Welcome @ArafatAbdussalam! It looks like this is your first PR to kubeedge/website 🎉

[ArafatAbdussalam]

/assign

[ArafatAbdussalam]

Hi @fisherxu @edisonxiang @Shelley-BaoYue I will be glad if you could help review this PR referenced to #347 for LFX'23 Sep Term. Here is the proposed change in the images below:

[kubeedge-bot]

@ArafatAbdussalam: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.