🪲 Fix logic to compare compute setting to static counterparts, rather than evaluating static ComputeSetting directly

[QuitCrypto]

The existing logic evaluates static compute setting values as conditions for ternary expressions, which will always evaluate truthy. They should instead be comparing the existing compute setting to their static counterparts.

[yargo13]

Nice catch, thanks! Can you generate a changeset with pnpm changeset ?

[yargo13]

Also saw that linter failed, fix would be

            const mapper =
                computeSetting === ComputeSetting.OnlyReduce
                    ? (this.logger.info('OnlyReduce setting is used. Skipping map step.'),
                      (r: RequestResponsePair) => r.response)
                    : (r: RequestResponsePair) => this.lzMap(compute, r, timeMarker)
            const reducer =
                computeSetting === ComputeSetting.OnlyMap
                    ? (this.logger.info('OnlyMap setting is used. Skipping reduce step.'),
                      (mappedResponses: string[]) => mappedResponses.join(''))
                    : (mappedResponses: string[]) => this.lzReduce(compute, cmd, mappedResponses, timeMarker)

[yargo13]

Let's put it as patch. It also picked up another commit, but I think that is fine

[QuitCrypto]

Re-marked it as a patch and rebased to sync it up with main again