Use a different socks port number for channel ''.

[riastradh-brave]

Channel '' apparently happens for local builds, and we don't want it
to step on the toes of release builds.

fix #14592

This is a stop-gap measure until we use an OS-chosen socks port
number or a local socket as in #12936.

Auditors: @diracdeltas @bsclifton

Submitter Checklist:

• Submitted a ticket for my issue if one did not already exist.
• Used Github auto-closing keywords in the commit message.
• Added/updated tests for this change (for new code or code which already has tests).
• Ran git rebase -i to squash commits (if needed).
• Tagged reviewers and labelled the pull request as needed.
• Request a security/privacy review as needed. (Ask a Brave employee to help if you cannot access this document.)

Test Plan:

1. Launch a local development build of Brave.
2. Laucnh a release build of Brave.
3. Confirm that Tor works in both.

Reviewer Checklist:

• Request a security/privacy review as needed if one was not already requested.

Tests

• Adequate test coverage exists to prevent regressions
• Tests should be independent and work correctly when run individually or as a suite ref
• New files have MPL2 license header

[diracdeltas]

this lgtm but i would like @bsclifton to confirm this logic since i also don't know what all the channels correspond to

[bsclifton]

Can you actually make a separate case (with a different port number) for ''? Local builds are their own channel (kind of)- but in the code, they are treated as dev (we never made a local channel)

[bsclifton]

Beautiful 😄👌

[bsclifton]

master faff16a
0.24.x 08c2552
0.23.x 3d5d338