test(aries): refactor jest test negative test cases

[ashnashahgrover]

Commit to be reviewed

test(aries): refactor jest test negative test cases

Primary Changes
----------------
1. Refactored all the negative test case exception assertions for
cactus-plugin-ledger-connector-aries. Removed try-catch blocks,
replaced with declarations through jest-extended's own API.

Fixes #3473

Pull Request Requirements

• [ ] Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• [ ] Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• [ ] Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• [ ] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• [ ] Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners For rebasing and squashing, here's a must read guide for beginners.

[jagpreetsinghsasan]

@ashnashahgrover the pr-commit parity checker is failing because your PR message contains a special character after Primary Changes This is how it is getting rendered in my mail

I then updated your PR message and now when I run it, it still fails as there is diff (very minute)

I have updated it again and it still fails and now this is something which my upcoming patch for the CI test will fix. (Please do not spend any time on fixing the Commit Parity check)

[ashnashahgrover]

LGTM, thank you!

Please run yarn run lint to format sources and fix the lint CI error

Done.