Dissociate accounts from tokens post run

[Nana-EC]

Detailed description:
Many of the HTS acceptance tests associate the payer account with the newly created token.
Overtime this may build up and the account may hit the TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED error.

Full @acceptance runs are also expensive and it might be worth being a bit more selective on tests included for every post deployment run

• Dissociate accounts from tokens post run
• Add @critical and @release flags for acceptance tests, refine tag distribution accordingly
• Update README
• Where possible use payer account as treasury as it avoids the cost of creating and funding a new treasury account
• Reduce funding amounts for created accounts to cut costs
• Remove camel case tag variants

Which issue(s) this PR fixes:
Fixes #2069

Special notes for your reviewer:
A full @acceptance run was costing about 150 ℏ, with these updates I was able to cut it down to 36 ℏ

@acceptance - total cost 31.6  ℏ
@release - total cost 19.2  ℏ
@critical -  total cost 6.5  ℏ

Checklist

• Documentation added
• Tests updated

[codecov]

Codecov Report

Merging #2090 (2f194bf) into master (126751e) will decrease coverage by 7.60%.
The diff coverage is 87.42%.

@@             Coverage Diff              @@
##             master    #2090      +/-   ##
============================================
- Coverage     87.05%   79.44%   -7.61%     
- Complexity     1744     1920     +176     
============================================
  Files           315      377      +62     
  Lines          7731     9304    +1573     
  Branches        740      879     +139     
============================================
+ Hits           6730     7392     +662     
- Misses          772     1649     +877     
- Partials        229      263      +34     

Impacted Files	Coverage Δ
...ensus/ConsensusCreateTopicTransactionSupplier.java	0.00% <ø> (ø)
...sus/ConsensusSubmitMessageTransactionSupplier.java	0.00% <0.00%> (ø)
...ensus/ConsensusUpdateTopicTransactionSupplier.java	0.00% <ø> (ø)
...er/schedule/ScheduleCreateTransactionSupplier.java	0.00% <ø> (ø)
...supplier/token/TokenCreateTransactionSupplier.java	0.00% <ø> (ø)
...supplier/token/TokenUpdateTransactionSupplier.java	0.00% <ø> (ø)
...ra/mirror/monitor/config/MonitorConfiguration.java	0.00% <0.00%> (ø)
...edera/mirror/monitor/publish/PublishException.java	0.00% <0.00%> (ø)
.../hedera/mirror/monitor/publish/PublishMetrics.java	0.00% <0.00%> (ø)
...a/mirror/monitor/publish/TransactionPublisher.java	1.09% <0.00%> (-0.04%)	⬇️
... and 181 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bfe92d7...2f194bf. Read the comment docs.

[xin-hedera]

just some minor issues

[ijungmann]

Looks good, couple small things.

[ijungmann]

Should we set the default Dockerfile command to use @critical or @release instead of @balancecheck?

[Nana-EC]

Should we set the default Dockerfile command to use @critical or @release instead of @balancecheck?

Should be @critical thought I fixed that
Ah I see now. I'd say @critical makes sense as a balance check may not catch certain issues with the network

[sonarcloud]

SonarCloud Quality Gate failed.

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

0.0% Coverage
3.2% Duplication

[xin-hedera]

LGTM

[steven-sheehy]

LGTM