Fix CONFIG SET test failures in MacOS/FreeBSD (#9881)
Fix CONFIG SET test failures in MacOS/FreeBSD (#9881)

After the introduction of `Multiparam config set` in #9748,
there are two tests cases failed.

```
[exception]: Executing test client: ERR Config set failed - Failed to set current oom_score_adj. Check server logs..
ERR Config set failed - Failed to set current oom_score_adj. Check server logs.
```

`CONFIG sanity` test failed on the `config set oom-score-adj-values`
which is a "special" config that does not catch no-op changes.
And then it will update `oom-score-adj` which not supported in
MacOs. We solve it by adding `oom-score*` to the `skip_configs` list.

```
*** [err]: CONFIG SET rollback on apply error in tests/unit/introspection.tcl
Expected an error but nothing was caught
```

`CONFIG SET rollback on apply error` test failed on the
`config set port $used_port`. In theory, it should throw the
error `Unable to listen on this port*`. But it failed on MacOs.
We solve it by adding `-myaddr 127.0.0.1` to the socket call.

yossigo/redis,ofirluzon/redis,ofirluzon/redis,antirez/redis,antirez/redis,soloestoy/redis,neomantra/redis,PKRoma/redis,soloestoy/redis,PKRoma/redis,charsyam/redis,yossigo/redis,PKRoma/redis,oranagra/redis,neomantra/redis,yossigo/redis,charsyam/redis,ofirluzon/redis,PKRoma/redis,oranagra/redis,neomantra/redis,neomantra/redis,PKRoma/redis,soloestoy/redis,ofirluzon/redis,soloestoy/redis,charsyam/redis,antirez/redis,charsyam/redis,yossigo/redis,ofirluzon/redis,yossigo/redis,oranagra/redis,charsyam/redis,oranagra/redis,neomantra/redis,oranagra/redis,soloestoy/redis,antirez/redis