Add defaultChainId as an option parameter

[alepc253]

Description

This PR is a proposal for issue #2743.

Adds defaultChainId as an option parameter (undefined as default) that would be used in input validation and output formatting for addresses, considering changes included in PR #2727.

Type of change

• New feature
• Breaking change
• Enhancement

Checklist:

• I have selected the correct base branch.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no warnings.
• I have updated or added types for all modules I've changed
• Any dependent changes have been merged and published in downstream modules.
• I ran npm run test in the root folder with success and extended the tests if necessary.
• I ran npm run build in the root folder and tested it in the browser and with node.
• I ran npm run dtslint in the root folder and tested that all my types are correct
• I have tested my code on an ethereum test network.

[coveralls]

Coverage increased (+0.02%) to 95.965% when pulling 283dde2 on alepc253:validators-and-formatters into dc63f75 on ethereum:1.0.

[coveralls]

Coverage increased (+0.02%) to 95.965% when pulling 283dde2 on alepc253:validators-and-formatters into dc63f75 on ethereum:1.0.

[nivida]

I would like to keep the internal address validation the same as before and we have implemented this standard already with the updated utility methods.

[alepc253]

@nivida yes, the utility methods are implemented but if you pass a type address parameter checksummed with this standard to any of the web3 methods, it will be rejected for bad checksum.