Update config to fix warnings

Why is this change being made?

Update config to fix warnings

Fixes #560 (closed)

(changes made by DAP 😁)

Summary from Agentic Chat:

Summary

I've successfully implemented the fixes for issue #560 (closed) to address the Hugo build warnings. Here are the changes made to config/_default/config.yaml:

1. Fixed deprecated config key (Line ~103)
   • Changed: markup.goldmark.renderHooks.link.enableDefault: true
   • To: markup.goldmark.renderHooks.link.useEmbedded: fallback
   • Reason: Hugo 0.148.0 deprecated enableDefault in favor of useEmbedded. Using fallback maintains the same behavior as the previous true value.
2. Increased sidebar menu truncation limit (Line ~40)
   • Changed: params.ui.sidebar_menu_truncate: 120
   • To: params.ui.sidebar_menu_truncate: 125
   • Reason: The build warning indicated that 5 sidebar entries were being truncated. Increasing the limit to 125 will prevent this truncation for the /handbook/support/workflows section.
3. Removed duplicate module import (Lines ~119-121)
   • Removed: The theme: section that listed both gitlab.com/gitlab-com/content-sites/docsy-gitlab and github.com/google/docsy
   • Reason: These modules were already properly declared in the module.imports section below. Having them in both places caused Hugo to import docsy-gitlab v0.3.63 twice, triggering the duplicate import warning. When using Hugo modules, the module.imports section is the correct place to declare them.

All three warnings from the build logs should now be resolved:

• ✅ No more deprecation warning about enableDefault
• ✅ No more duplicate module import warning
• ✅ No more sidebar truncation warning

The changes are minimal and focused only on addressing the specific warnings mentioned in the issue, without affecting any other functionality.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct
  • The when to get approval handbook section explains when DRI approval is required
  • The who can approve handbook section explains how to identify the DRI
  • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
  • The approver may merge the MR. If they approve but don't merge, you can merge.
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Update config to fix warnings

---