(Fix) Investors incorrect max cap

[fernandomg]

Closes #1067

This PR fixes all the related issues with whitelisted addresses and tier's supply. Scenarios that I took into account for both strategies (MintedCapped and DutchAuction):

• Whitelists addresses added (from CSV, manually or combined), will be limited to the sum of maxCap that is not greater than tier's supply. i.e.: for addresses with maxCap of [100, 200, 300] if supply is 400, then only the first two addresses will be added.
• If after adding whitelist addresses, the supply value will be validated against the sum of the maxCaps. It should not be less than the maxCap sum.
• In the manage screen supply cannot be edited, so whitelist addresses will be checked.

Note The scenario that I didn't fix, due to the complexity of the fix itself (it would require several modifications and would be better to address it in a separate PR), has to be with manage screen and an address values modification.

As you can see in the screenshot Despite having 1011 tokens available, and requiring only 28 extra tokens to change 1972 to 2000, it's giving the error as it considers that the address is new and not a modification of an existing one.

---

Also:

• tests where updated and fixed
• linting errors where solved

[dennis00010011b]

@fernandomg Manage page: allowed to add whitelisted investors with maxCap greater than remained token's supply. Steps:

1. Create Minted crowdsale, 1 tier:
   • supply =1000
   • whitelisted address with maxCap=300
2. As whitelisted investor buy maxCap
3. As an owner open manage page
4. Add another whitelisted investor with maxCap=supply

Expected result:

• whitelisted maxCap should be restricted by supply-300=700

Actual result:

• it is possible to add whitelisted address wjth maxCap >700

[fernandomg]

@dennis00010011b that was quick! thanks for the catch, will review it

[BlackDuckCoPilot]

Black Duck Security Report

Merging #1072 into 2.0 will not change security risk.

Removed Components

Clean: 2

Click here to see full report

[fernandomg]

Ok, so after reviewing the different scenarios that will arise with this PR and have a chat with @vbaranov. It was decided to close this PR and create a new solution for #1067, which is https://github.com/poanetwork/token-wizard/issues/1067#issuecomment-411397561