CCM-10447 Update for new failed reason codes

[Ian-Hodges]

Summary

Updates for new messageFailureReasonCode and channelFailureReasonCode fields returned by the get message endpoint.

• Examples added to the sandbox responses.
• Specification document updated.
• New successful failed status e2e test.

Test Evidence

Test evidence added to CCM-10447.

Reviews Required

• Dev
• Test
• Tech Author
• Product Owner

Checklist

• Brief description of work completed, and any technical decisions made as part of the PR
• PR link added as a comment to the relevant JIRA ticket
• PR link shared on Slack and/or Teams
• 2 reviews received
• Tester approval

[github-actions]

This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket:

CCM-10447

[simonlabarere]

Is this test potentially showing an issue with comms-mgr?

FAILED tests/api/message_batches/test_201_success.py::test_201_message_batch_terminal_failed_status - AssertionError: assert 
  None
  
    ==
  'MFR_CFGV_0005'
FAILED tests/api/single_message/test_201_success.py::test_201_message_terminal_failed_status - AssertionError: assert 
  None
  
    ==
  'MFR_CFGV_0005'

[Ian-Hodges]

Is this test potentially showing an issue with comms-mgr?

FAILED tests/api/message_batches/test_201_success.py::test_201_message_batch_terminal_failed_status - AssertionError: assert 
  None
  
    ==
  'MFR_CFGV_0005'
FAILED tests/api/single_message/test_201_success.py::test_201_message_terminal_failed_status - AssertionError: assert 
  None
  
    ==
  'MFR_CFGV_0005'

It's because it's no longer pointing to de-iaho3 and internal-dev doesn't have the changes yet. There's evidence of a successful deployment in the ticket.