Bump Server version to 0.0.0-rodrigozhou-0

Bump Server version to 1.23.0-rodrigozhou-test-3

Bump Server version to 1.23.0-rodrigozhou-test-2

Bump Server version to 1.23.0-rodrigozhou-test

Fix nil panic (temporalio#5153)

<!-- Describe what has changed in this PR -->
**What changed?**
Add nil check when using namespaceEntry

<!-- Tell your future self why have you made these changes -->
**Why?**
nil panic found at edge case

<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
**How did you test it?**
n/a

<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
**Potential risks**
no

<!-- Is this PR a hotfix candidate or require that a notification be
sent to the broader community? (Yes/No) -->
**Is hotfix candidate?**
no

Bump server version to 1.23.0 (temporalio#5173)

## What changed?
<!-- Describe what has changed in this PR -->
^

## Why?
<!-- Tell your future self why have you made these changes -->
We need to do this on main _before_  we cut 1.23.0-rc1

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->

1.22.3 build fix for cherry pick build error (temporalio#5163)

## What changed?
1.22.3 build fix for cherry pick build error

## Why?
<!-- Tell your future self why have you made these changes -->

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->

Fix set up search attributes in secondary SQL visibility (temporalio#…

…5143)

<!-- Describe what has changed in this PR -->
**What changed?**
Fix setting up pre-allocated search attributes when a secondary SQL
visibility is added.

<!-- Tell your future self why have you made these changes -->
**Why?**
PR temporalio#4531 removed code that
did this.

<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
**How did you test it?**
Started single SQL visibility, and then added secondary SQL visibility.
Checked cluster metadata, it looks right.

<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
**Potential risks**
No.

<!-- Is this PR a hotfix candidate or require that a notification be
sent to the broader community? (Yes/No) -->
**Is hotfix candidate?**
No.

Add action metrics for schedule and updates (temporalio#5101)

<!-- Describe what has changed in this PR -->
**What changed?**
Add more action metrics for schedules and updates

<!-- Tell your future self why have you made these changes -->
**Why?**
Add more actions

<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
**How did you test it?**
eye_balls

<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
**Potential risks**
No

<!-- Is this PR a hotfix candidate or require that a notification be
sent to the broader community? (Yes/No) -->
**Is hotfix candidate?**
No

Allow list of keywords in dual visibility setting (temporalio#5065)

<!-- Describe what has changed in this PR -->
**What changed?**
Allow list of keywords in dual visibility setting

<!-- Tell your future self why have you made these changes -->
**Why?**
Let dual visibility with Elasticsearch work with list of keywords for
backwards compatibility.

<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
**How did you test it?**


<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
**Potential risks**
No. Any setting involving standard visibility will work as usual: custom
search attributes are just ignored and not persisted.

<!-- Is this PR a hotfix candidate or require that a notification be
sent to the broader community? (Yes/No) -->
**Is hotfix candidate?**
No.