Chore: TC cleanup

[roxdanila]

Context

Found it really tricky to navigate the contract as I was reviewing emergency pause usage.

Changes proposed in this pull request

Grouped functions together in the following categories, for easier navigation:

• CONSTRUCTOR
• WHITELIST RELATED MUTATIVE FUNCTIONS
• TOKEN RELATED VIEW FUNCTIONS
• INTERNAL OPERATOR RELATED MUTATIVE FUNCTIONS
• USER REWARDS RELATED MUTATIVE FUNCTIONS
• V1 RELATED VIEW FUNCTIONS
• V1 RELATED MUTATIVE FUNCTIONS
• DEPENDENCIES

This is what made sense to me without spending too much time on it. I hope this won't stir an opinionated debate, but if think something doesn't make sense, let me know.

Test plan

Existing tests pass.

Checklist

• Rebased the base branch
• Attached corresponding Github issue
• Prefixed the name with the type of change (i.e. feat, chore, test)
• Performed a self-review of my own code
• Followed the style guidelines of this project
• Made corresponding changes to the documentation
• Didn't generate new warnings
• Didn't generate failures on existing tests
• Added tests that prove my fix is effective or that my feature works

Review

When reviewing a PR, please indicate intention in comments using the following emojis:

• 🍰 = Nice to have but not essential.
• 💡 = Suggestion or a comment based on personal opinion
• 🔨 = I believe this should be changed.
• 🤔 = I don’t understand something, do you mind giving me more context?
• 🚀 = Feedback

[shark0der]

Will conflict with feature/staking-nft. Let's rebase it after that one is merged.

[roxdanila]

Closing in favour of #611