Fix conditions for red color text in remaining display widgets

[chinins]

Description

This PR fixes the conditions for color coding of the remaining display widgets (time & tokens)

Changes 🏗

• simplify props passing in RemainingTokensValue
• update isWarning conditions in RemainingTokens & RemainingTime

Resolves #3012

[arrenv]

Working as expected, nice work!

I do have a couple of other things I noticed that you may also be able to include in this PR. However, let me know if you think these should be raised in separate issues.

#1 - Sold out warning on batches is not displaying if the total tokens in the coin machine are sold out.

#2 - Available tokens on batches not correct.

[chinins]

@arrenv, regarding the sold out issue I will fix it in this PR.

Regarding the second issue with incorrect amounts, I think it should be a different issue. Do you have any per user purchase limit that might intervene with this or anything else? I didn't experience this issue.

[arrenv]

It is all default, as in the per user limit is 100% and batch size is 400,000.

You do have to let the next batch start though, which is why I skipped forward an hour. I ran the following in terminal.

curl -H "Content-Type: application/json" -X POST --data '{"jsonrpc":"2.0","method":"evm_increaseTime","params":[3600],"id": 1}' localhost:8545 && curl -H "Content-Type: application/json" -X POST --data '{"jsonrpc":"2.0","method":"evm_mine","params":[]}' localhost:8545

[chinins]

@arrenv, can you please test the token numbers & soldout issues again? Maybe there is something wrong with pulling data from the contracts... The logic is working properly for me (and I had less tokens left than the target):

[ArmandoGraterol]

For me, the color of all 3 widgets is working as expected! And I agree that the second issue should be separated as it's not related to this PR and it may not be a simple, small fix.

[arrenv]

@chinins I have been trying to replicate again today with a fresh environment and have not been able to replicate. So, like you said, probably just an environment issue.

Regarding #2 this still seems to be an issue, so I will raise that separately.