feat: custom protocol name

[greenSnot]

No description provided.

[vasco-santos]

Thanks for adding this support. I left a couple of suggestions to get this to the finish line

[vasco-santos]

Awesome, looks much cleaner now!
We should just add a test file in https://github.com/libp2p/js-libp2p/tree/master/test/configuration where we configure a different prefix and verify if node.peerStore.protoBook.get(node.peerId) contains the expected protocols

[greenSnot]

Done

[vasco-santos]

@greenSnot there is still one issue that we need to solve. The linting job is failing with the following errors

/home/runner/work/js-libp2p/js-libp2p/src/identify/consts.js:15:67: Newline required at end of file but not found. [Error/eol-last]
/home/runner/work/js-libp2p/js-libp2p/src/identify/index.js:49:24: Missing space before function parentheses. [Error/space-before-function-paren]
/home/runner/work/js-libp2p/js-libp2p/src/identify/index.js:52:154: Unexpected trailing comma. [Error/comma-dangle]

/home/runner/work/js-libp2p/js-libp2p/src/ping/constants.js:7:24: Unexpected trailing comma. [Error/comma-dangle]
/home/runner/work/js-libp2p/js-libp2p/src/ping/index.js:33:19: Multiple spaces found before '`/${'. [Error/no-multi-spaces]
/home/runner/work/js-libp2p/js-libp2p/src/ping/index.js:33:91: Extra semicolon. [Error/semi]

/home/runner/work/js-libp2p/js-libp2p/test/configuration/protocol-prefix.node.js:17:37: Unexpected trailing comma. [Error/comma-dangle]

You can run npm run lint to run it locally.

[vasco-santos]

@greenSnot apologies, but you will need to rebase this PR. We had an issue in CI that I saw in this PR and I already fixed it in #963 but now we need a rebase to get this fixed here and get CI jobs green

[vasco-santos]

LGTM
Thanks for getting this to the finish line