feat(authors): add a per-author name-highlight flag (owner by default)

[Vidminas]

page_metadata_authors already had a $highlight_name flag and a font-bold branch, but it was hardcoded to false, so author names were never emphasised in citation/publication author lists.

Add an optional per-author highlight_name bool (surfaced by get_author_profile) that controls whether an author's name is emphasised:

• set highlight_name: true to highlight any author (e.g. yourself as a co-author), or false to opt out;
• when unset it falls back to is_owner (from is_owner: true / legacy superuser: true), so the site owner is highlighted by default.

The fallback uses ne … nil rather than | default so an explicit highlight_name: false opts the owner out instead of being read as unset.

Documented in get_author_profile's output contract (header comment) and as a commented example in the academic-cv me.yaml author file.

🚀 What type of change is this?

• 🐛 Bug fix (A non-breaking change that fixes an issue)
• ✨ New feature (A non-breaking change that adds functionality)
• 💅 Style change (A change that only affects formatting, visuals, or styling)
• 📚 Documentation update (Changes to documentation only)
• 🧹 Refactor or chore (A code change that neither fixes a bug nor adds a feature)
• 💥 Breaking change (A fix or feature that would cause existing functionality to not work as expected)

---

🎯 What is the purpose of this change?

page_metadata_authors.html already contains a $highlight_name variable and a font-bold
render branch — but $highlight_name is hardcoded to false and never set, so author names
are never emphasised in a citation or publication author list.

Change. Add an optional per-author highlight_name bool (surfaced by get_author_profile)
that controls whether that author's name is emphasised:

• highlight_name: true → highlight this author (e.g. yourself as a co-author); false → opt out;
• when unset, it defaults to is_owner (from is_owner: true, or the legacy superuser: true),
  so the site owner is bold out of the box with no extra config.

So the owner is highlighted by default, but it's no longer forced — any author can opt in or out,
and the owner can opt out. It's a single author-data field alongside the existing is_owner; no
block- or site-level config knob is added. The fallback uses ne … nil (not | default) so an
explicit highlight_name: false opts the owner out rather than being read as "unset".

Verified on the academic-cv starter (data/authors/me.yaml has is_owner: true):

• default — the owner "Dr. Alex Johnson" renders font-bold (3×) in the homepage "Recent
  Publications" list, co-authors plain; on main nothing is bold;
• owner opts out (highlight_name: false on me.yaml) — the owner renders plain;
• co-author opts in (highlight_name: true on a co-author's data file) — that name renders font-bold.

---

📸 Screenshots or Screencast (if applicable)

The homepage "Recent Publications" (citation view) on the academic-cv starter, in both light and
dark themes. The owner "Dr. Alex Johnson" is emphasised, while co-author "Robert Ford"
stays regular weight — so the owner's name stands out in the multi-author citations.

Before — main (owner's name plain, indistinguishable from co-authors):

Light	Dark

After — this PR (owner's name bold):

Light	Dark

---

ℹ️ Documentation Check

• No, this change does not require a documentation update.
• Yes, I have updated the documentation accordingly (or will in a follow-up PR).

Documented in-branch: the field is listed in get_author_profile.html's output contract (its
header comment), and shown as a commented, explained example next to is_owner in the academic-cv
me.yaml author file.

(Only academic-cv's me.yaml carries the example so far; happy to mirror it into the other starters' author files if the maintainers would prefer. The hosted docs at docs.hugoblox.com also need highlight_name added
to the author-data reference.)

---

📜 Contributor Agreement

Thank you for your contribution!

• By checking this box, I confirm that I have read and agree to the HugoBlox Contributor License Agreement (CLA).

[netlify]

❌ Deploy Preview for academic-demo failed. Why did it fail? →

Name	Link
🔨 Latest commit	0fae3ab
🔍 Latest deploy log	https://app.netlify.com/projects/academic-demo/deploys/6a537b33790a8f00084a8612

[Vidminas]

Builds fail due to Hugo 0.162.0 incompatibility, which is addressed in #3329