[Do not merge] update build.json for new deployment bundle

[c12simple]

Change type

• Fix
• Feature
• Documentation
• Security / Upgrade

Basic information

• THIS CHANGE REQUIRES A DEPLOYMENT PACKAGE RELEASE
• THIS CHANGE REQUIRES A WIRE-DOCS RELEASE

Testing

• I ran/applied the changes myself, in a test environment.
• The CI job attached to this repo will test it for me.

Offline Build CI (label-based)

Add one or more labels to trigger offline builds:

• build-default - Full production build (ansible, terraform, all packages)
• build-dev - WIAB/dev build
• build-wiab-staging - WIAB-staging build
• build-min - Minimal build (fastest, essential charts only)
• build-all - Run all three builds

Note: No builds run by default. Add a label to trigger CI.

Tracking

• I added a new entry in an appropriate subdirectory of changelog.d
• I mentioned this PR in Jira, OR I mentioned the Jira ticket in this PR.
• I mentioned this PR in one of the issues attached to one of our repositories.

Knowledge Transfer

• An Asciinema session is attached to the Jira ticket.

Motivation

Objective

Reason

Use case

[mohitrajain]

@c12simple please fill in the description by selecting the following:
Change type = Upgrade
Basic information = THIS CHANGE REQUIRES A DEPLOYMENT PACKAGE RELEASE
Testing = The CI job attached to this repo will test it for me.
Tracking : add the ticket number in description eg.. WPB-12345 and a changelog entry as per: https://keepachangelog.com/en/1.1.0/

Also, another suggestion for PRs which aren't meant to be merged or takes time - feel free to click on "Still in progress? Convert to draft". This will save someone accidentally clicking on merge and your github workflows can still run. :)
Thanks