caller_addresses: use input_message_recipient (#6649)

## Description

Closes #6648 

## Checklist

- [x] I have linked to any relevant issues.
- [x] I have commented my code, particularly in hard-to-understand
areas.
- [x] I have updated the documentation where relevant (API docs, the
reference, and the Sway book).
- [x] If my change requires substantial documentation changes, I have
[requested support from the DevRel
team](https://github.com/FuelLabs/devrel-requests/issues/new/choose)
- [x] I have added tests that prove my fix is effective or that my
feature works.
- [x] I have added (or requested a maintainer to add) the necessary
`Breaking*` or `New Feature` labels where relevant.
- [x] I have done my best to ensure that my PR adheres to [the Fuel Labs
Code Review
Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md).
- [x] I have requested a review from the relevant team or maintainers.

Co-authored-by: Joshua Batty <joshpbatty@gmail.com>

sway-lib-std/src/auth.sw

@@ -231,7 +231,7 @@ pub fn caller_addresses() -> Vec<Address> {
         // Call the corresponding function based on the input type.
         let input_owner = match input_type(iter) {
             Some(Input::Coin) => input_coin_owner(iter),
-            Some(Input::Message) => input_message_sender(iter),
+            Some(Input::Message) => input_message_recipient(iter),
             _ => None, // If not Coin or Message, loop continues.
         };