Remove all irrelvent content from blogs branch to prepare blog migration

[ashishksdev]

What changes were proposed in this pull request?

This PR removes all existing content from the blogs branch to prepare it for migration of blog content from the main branch. The blogs branch was originally created from versioned-docs and contained unrelated files that need to be cleared before adding the actual blog content.
This is Part 1 of 2 for issue #2774:
Part 1 (this PR): Clean the blogs branch by removing all existing files
Part 2 (follow-up PR): Add blog content from main branch with preserved author information

Why are the changes needed?
As discussed in issue #2774, the blog content needs to be moved to a separate blogs branch. However, the blogs branch currently contains files from versioned-docs that are not related to blogs.
Separating the cleanup and addition into two PRs makes the changes easier to review and addresses feedback from previous attempts where mixing both operations caused:
Difficulty in reviewing the changes
Unintended modifications to files
Confusion in the diff

Does this PR introduce any user-facing change?
No.

How was this patch tested?
Verified locally that:
All files are properly removed from the blogs branch
The diff shows only deletions with no modifications
The branch structure remains intact

CHANGELOG.md
Not applicable - this is an internal repository reorganization with no user-facing changes.

[ashishksdev]

This is Part 1 of the cleaner approach. This PR removes all existing content from the blogs branch as discussed.
Once this is reviewed/merged, I'll follow up with Part 2 to add the blog content with preserved author information.
Please let me know if this approach looks good or if you'd like any changes!
@flyrain @dimas-b

[dimas-b]

This PR removes docs from the blogs branch, while the blogs branch appears to be based on versioned-docs.

What is the reason for this branching approach?

I'd prefer to work out an impl. approach in this dev thread before starting PRs: https://lists.apache.org/thread/dfyv0c6g53qw3vjxcb1nqy3myb6yc8q1

ATM I do not think there was any consensus on the impl. side there while the current proposal calls for branching blogs from main, not from versioned-docs.

[ashishksdev]

Thanks @dimas-b and @flyrain for the detailed explanation on the mailing list.

I'm closing this PR since the approach has evolved from what was originally discussed. This PR was based on the earlier instruction to clean the versioned-docs-based blogs branch, but I understand from the mailing list discussion that the preference is now to have the blogs branch created from main to preserve Git author associations.

I'm happy to contribute once things are ready - specifically once the blogs branch is recreated based on main (as the current blogs branch is based on versioned-docs) and after any further discussion and decisions are finalized.

[flyrain]

Thanks @ashishksdev for keeping working on it. Created a new branch blogs based on the main. Let me know if any help is needed.