[bn] Merge dev-bn branch into main branch

[sajibAdhi]

Describe your changes

Merge the dev-bn branch into the main branch.

Related issue number or link (ex: resolves #issue-number)

#410

Checklist before opening this PR (put x in the checkboxes)

• This PR does not contain plagiarism
  • don’t copy other people’s work unless you are quoting and contributing it to them.
• I have signed off on all commits
  • signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

[netlify]

✅ Deploy Preview for cncfglossary ready!

Name	Link
🔨 Latest commit	6ffe849
🔍 Latest deploy log	https://app.netlify.com/sites/cncfglossary/deploys/66e1176d2a734c0008538898
😎 Deploy Preview	https://deploy-preview-3301--cncfglossary.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[asem-hamid]

@sajibAdhi , The dev-bn branch is behind a lot of changes, and several files need to be updated.

/hold , until then

[github-actions]

Wait, please do not proceed with this yet.

[github-actions]

Wait, please do not proceed with this yet.

[jihoon-seo]

To who merge this PR: please use 'Squash and merge' method when merging.

[seokho-son]

@asem-hamid do you have a plan to unhold this PR?

@sajibAdhi just hope to let you know, this PR has many meaningless commits considering the number of changed files. We recommend localization approvers handle commit history well. (make a localization PR has one commit if possible). Please share this to he team approves. :)

FYI, This PR will be merged by squash merge method.

[asem-hamid]

@seokho-son No, actually, we are quite behind. We have a small team, so we have to move forward slowly.

Also, we are trying to follow the '1 commit per PR' rule now. However, those meaningless commits are there for historical reasons. In the early days, the team didn't follow the '1 commit per PR' policy strictly, so the dev-bn branch became a junkyard for these commits.

As a result, when we merge the dev-bn branch into the main branch, the maintainer has to use the 'merge by squash' method. Every time we do this, only one commit gets added to the commit history (in the main branch), and the rest of the commits become junk in the dev-bn branch. It has become a repetitive cycle.

To break this cycle, we can take the following step:

After merging this PR (by squash method), we can simply delete the dev-bn branch (if possible) and create a new branch (based on main) with the same name. We'll be careful so that we don't face this issue again.

Please correct me if I’m wrong and share your opinion.