Store stack trace in a separate filed during logging

[jianglai]

For reasons unclear to me, if the stack trace is appended directly to
the message, the log entry will be lumped together with following logs
on GKE.

Also updated the GKE service account for Nomulus in the manifest so we
can use workload identity just for Nomulus, not other pods on the same
cluster.

---

This change is 

[jianglai]

Reviewed 4 of 4 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @jianglai)

[weiminyu]

Reviewed 2 of 4 files at r1.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @jianglai)

---

util/src/main/java/google/registry/util/GcpJsonFormatter.java line 111 at r1 (raw file):

      stacktrace = sw.toString();
    }
    String message = '\n' + record.getMessage() + stacktrace;

Could you try appending \r\n to the stack trace and see if it helps?

The fluent rules for collecting multi-line logs is at https://github.com/GoogleCloudPlatform/fluent-plugin-detect-exceptions/blob/8e5608209d9c2a8927b4531b2077f7057d65616c/lib/fluent/plugin/exception_detector.rb#L54,

and it seems that '\r\n` would help.

Code quote:

 stacktrace

[jianglai]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @weiminyu)

---

util/src/main/java/google/registry/util/GcpJsonFormatter.java line 111 at r1 (raw file):

Previously, weiminyu (Weimin Yu) wrote…

Could you try appending \r\n to the stack trace and see if it helps?

The fluent rules for collecting multi-line logs is at https://github.com/GoogleCloudPlatform/fluent-plugin-detect-exceptions/blob/8e5608209d9c2a8927b4531b2077f7057d65616c/lib/fluent/plugin/exception_detector.rb#L54,

and it seems that '\r\n` would help.

Tried it, didn't help :(

[weiminyu]

Reviewable status: 3 of 4 files reviewed, all discussions resolved (waiting on @jianglai)