Remove computation limits for the archive node

[vishalchangrani]

Currently, the archive node throws a computation limit exceeded error similar to the Execution node for scripts or transactions that require a lot of computation.
While it makes sense to have an execution node throw this error, it doesn't make sense for the archive node to throw it. An operator running an archive node should not be subjected to any computation limits on their own node.
This issue is to remove the computation limit from the archive node.