Blog index uses <nav> for tag/category links instead of <div>

[MelbourneDeveloper]

Problem

The blog index virtual template uses <nav class="blog-nav"> for the tags/categories link list:

<nav class="blog-nav">
  <a href="/blog/tags/" class="blog-nav-link">Tags</a>
  <a href="/blog/categories/" class="blog-nav-link">Categories</a>
</nav>

This creates a second <nav> element on the page alongside the main site navigation, which:

1. Violates the principle of having the primary <nav> be unique/identifiable
2. Causes Playwright strict mode violations when tests use page.locator('nav')
3. Is semantically incorrect - a couple of category/tag links isn't navigation

Expected behavior

Use <div> instead of <nav> for the blog tag/category links:

<div class="blog-nav">
  <a href="/blog/tags/" class="blog-nav-link">Tags</a>
  <a href="/blog/categories/" class="blog-nav-link">Categories</a>
</div>

The dart_node site uses <div class="blog-nav"> which doesn't create these conflicts.