layouts: use new try function

[l-zeuch]

Summary

Hugo 0.141.0 introduced a new try function, replacing the way error
handling is done. Update the affected render hooks and shortcodes such
that they no longer break on Hugo 0.141.0 and above.

Basic example

See gohugoio/hugo#13216 for migration instructions and further details.

Motivation

1. New users of this theme are likely to use the latest version of
   Hugo--ensure the build does not break for those.

2. Our CI (and probably most of other automated Hugo builds) is set to
   always use the latest extended version of Hugo. Without this change,
   we'd have to pin it to 0.140.2 or below.

Checks

• Read Creating a pull request
• Supports all screen sizes (if relevant)
• Supports both light and dark mode (if relevant)
• Passes npm run test (if relevant)

---

Some further remarks, which I wish to fully resolve before landing this
change. We can downgrade Hugo in our CI for the meantime.

Should we bump the minimum Hugo version in the affected files? I'm
seeing a minimum of 0.114.0 at the moment, checked individually.
Alternatively, should we just introduce a safeguard around the affected
block of code, checking if we are required to use try and do so
conditionally, based on the Hugo version in use?

Personally I'm leaning towards not touching that minimum version, and
instead wrap the affected blocks in a new safeguard. That way, we can
comfortably cut a patch-level release and not worry about a
(technically) breaking change. Please let me know what you think.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 032d88e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR