Update dependency ex_doc to v0.40.2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
ex_doc (source)	dev	patch	0.40.1 → 0.40.2	0.40.3

---

Release Notes

elixir-lang/ex_doc (ex_doc)

v0.40.2

Compare Source

• Bug fixes
  • Add rel="nofollow" to external links in HTML output
  • Use blockquote in llms.txt description
  • Void elements in epub, such wbr, must be terminated by the matching end-tag
  • Fix content container scrolling in older versions of Safari
  • Skip HTML comments when computing synopsis
  • Fix markdown backend code fence language and opaque type display
  • Fix false positive warning when linking to asset files
  • Prevent #search selector from impacting user content
  • Raise on extras that conflict with reserved filenames
  • Fix styling of admonition blocks

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: demo/mix.exs

Artifact update for ex_doc resolved to version 0.40.3, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 0.40.2
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/