fix: return 202 when challenge in createAuthorization response

[mcoburnmx]

Summary of Changes

Updated createAuthorization controller method to detect when a response contains a challenge and then sets the status code to 202. The motivation behind this change is that the client is wanting to support prompting the user to accept terms and conditions for Zelle before proceed to use the feature.

Fixes # HW2-1135

Public API Additions/Changes

Modified AuthorizationsController.createAuthorization() to detect challenge in response and alter status code to 202. No method signatures were changed.

Downstream Consumer Impact

This change should be transparent and should not impact downstream consumers.

How Has This Been Tested?

Tested it locally with a Path connector to verify getting back a 200 or 202 as desired. Also ran a project's authorization Arsenal tests against it to ensure they still passed.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works