Optimize/Correct the batch submit function

[CJPotter10]

Description

The design of the batch submit function was prior to the liveness and rewards tracking changes that were made that optimized the normal MsgSubmitValue workflow and reward tracking and did not get the changes and as a result not only was less efficient then it needs to be and could lead to some rewards being stuck in limbo

Related Issue

Fixes #

Type of Change

• [ x ] Bug fix
• New feature
• Documentation update
• State Changes (please describe)"
• [ x ] Chain Changes (please describe): update batch submit transaction to new liveness and reward tracking
• Daemon Changes
• Tests
• Added Getter

Testing

Updated tests to fit new flow

Checklist

• [ x ] Code follows project style guidelines
• [ x ] I have added appropriate comments to my code
• [ x ] I have updated the documentation accordingly
• [ x ] I have added tests that prove my fix or feature works
• [ x ] go test ./... is passing locally
• [ x ] make e2e is passing locally