GAWB-3824: Upgrade Akka again

[breilly2]

@davidangb was able to trace the error message back to scala-parser-combinators. There were a couple of changes in 1.1 that changed the quoting: scala/scala-parser-combinators#81 and scala/scala-parser-combinators#144. I started a FiaB with this branch and, this time, it showed the same single quotes that the tests were seeing, therefore I'm confident that updating the test expectations is the right thing to do.

• Submitter: Include the JIRA issue number in the PR description
• Submitter: Check that the Product Owner has signed off on any user-facing changes
• Submitter: Make sure Swagger is updated if API changes
  • ...and Orchestration's Swagger too!
• Submitter: If updating admin endpoints, also update firecloud-admin-cli
• Submitter: Check documentation and code comments. Add explanatory PR comments if helpful.
• Submitter: JIRA ticket checks:
  • Acceptance criteria exists and is met
  • Note any changes to implementation from the description
  • To Demo flag is set
  • Release Summary is filled out, if applicable
  • Add notes on how to QA
• Submitter: Update RC_XXX release ticket with any config or environment changes necessary
• Submitter: Database checks:
  • If PR includes new or changed db queries, include the explain plans in the description
  • Make sure liquibase is updated if appropriate
  • If doing a migration, take a backup of the
    dev
    and
    alpha
    DBs in Google Cloud Console
• Submitter: Update FISMA documentation if changes to:
  • Authentication
  • Authorization
  • Encryption
  • Audit trails
• Tell your tech lead (TL) that the PR exists if they want to look at it
• Anoint a lead reviewer (LR). Assign PR to LR

• Review cycle:
  • LR reviews
  • Rest of team may comment on PR at will
  • LR assigns to submitter for feedback fixes
  • Submitter rebases to develop again if necessary
  • Submitter makes further commits. DO NOT SQUASH
  • Submitter updates documentation as needed
  • Submitter reassigns to LR for further feedback

• TL sign off
• LR sign off
• Assign to submitter to finalize
• Submitter: Verify all tests go green, including CI tests
• Submitter: Squash commits and merge to develop
• Submitter: Delete branch after merge
• Submitter: Test this change works on dev environment after deployment. YOU own getting it fixed if dev isn't working for ANY reason!
• Submitter: Verify swagger UI on dev environment still works after deployment
• Submitter: Inform other teams of any API changes via Slack and/or email
• Submitter: Mark JIRA issue as resolved once this checklist is completed

[davidangb]

looks good to me; did not test