chore(deps): update build digest to 1ed1933

[renovate]

This PR contains the following updates:

Package	Update	Change
build	digest	cc14f9c -> 1ed1933

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[village-labs-bot]

upbound/configuration-app #67

Change Summary

• Submodule 'build' reference update from commit cc14f9c to 1ed1933

Potential Vulnerabilities

• File: build
• Code: ```
  -Subproject commit cc14f9cdac034e0eaaeb43479f57ee85d5490473
  +Subproject commit 1ed19332b947c449795fd016f3c21ee0a64930fd

- Explanation: Submodule updates can potentially introduce security vulnerabilities if the new commit contains unreviewed or malicious code. Without visibility into the changes within the submodule, it's impossible to assess the security impact.

## Code Smells
- File: `build`
- Code: ```
-Subproject commit cc14f9cdac034e0eaaeb43479f57ee85d5490473
+Subproject commit 1ed19332b947c449795fd016f3c21ee0a64930fd

• Explanation: Using git submodules can lead to dependency management complexity and make the codebase harder to maintain. Consider if the build dependency could be managed through other means like package managers or direct inclusion.

Debug Logs

None identified in the provided diff.

Unintended Consequences

• File: build
• Code: ```
  -Subproject commit cc14f9cdac034e0eaaeb43479f57ee85d5490473
  +Subproject commit 1ed19332b947c449795fd016f3c21ee0a64930fd

- Explanation: Updating a build submodule could potentially break the build process or introduce incompatibilities with the main project. Without context of the changes in the submodule, there's a risk of unexpected behavior.

## Risk Score: 6
The risk score is moderately high due to:
1. Lack of visibility into the actual changes within the submodule
2. Potential for breaking changes in build system
3. Security implications of pulling in new submodule code without clear review context

[kaessert]

/test-examples