Bump version: 0.35.1-rc0 → 0.35.1

chore: bump version: 0.35.1-rc0 -> 0.35.1

Bump version: 0.35.0 → 0.35.1-rc0

[AUTO-BACKPORT 10160] fix: maxPoolSlotCapacity bug (#10195)

Co-authored-by: John Kim <[email protected]>

[AUTO-BACKPORT 10182] docs: docs changes for searcher context removal (…

…#10194)

Co-authored-by: Anda Zhou <[email protected]>

[AUTO-BACKPORT 10174] docs: update docs for non-Trial-centric world (#…

…10186)

Co-authored-by: Ryan <[email protected]>

[AUTO-BACKPORT 10183] docs: fix typos in the release note (#10185)

Co-authored-by: Jerry G <[email protected]>

[AUTO-BACKPORT 10140] fix: set max slots and checkpoint gc policy sho…

…uld comply with config policies (#10167)

Co-authored-by: Amanda Vialva <[email protected]>

[AUTO-BACKPORT 10155] fix: fix iris example to use reported metric na…

…me (#10156)

Co-authored-by: Anda Zhou <[email protected]>

build: INFENG-942: Conditionally bypass build-react job checks (#10145)

The release job is skipping the React build step because there are two
jobs that attempt to skip the entire job if no changes are detected in
specific directories. Previously, bumpversion made it so that, by dint
of updating various files, the job would not be skipped. Now that we
aren't using it, though, certain downstream jobs are failing because
React wasn't built.

To fix this, I've added a "force" variable to the build-react job, to
allow conditionally bypassing the checks if indicated by the
caller. This preserves existing behavior, to avoid potentially other
unintended consequences of beginning to build React everywhere, but also
to avoid running up CircleCI compute bills, as this much extra build
time would probably have a material effect on spending.