### Summary

 When we updated `Display` to proxy over the queue for dispatch by the main process in https://github.com/ansible/ansible/pull/77056, we ended up losing some context, since we only proxy the `Display.display` method, and not all methods individually.

We need to add some functionality to `Display` to preserve this context, whether that means shipping additional information across the queue, or proxying all methods instead of just `Display.display`.

This has impacts on ansible-runner, and input should be taken to evaluate the best option.

### Issue Type

Feature Idea

### Component Name

lib/ansible/utils/display.py

### Additional Information

TBD

### Code of Conduct

- [X] I agree to follow the Ansible Code of Conduct
fileobj = sys.stdout
            else:
                fileobj = sys.stderr
            with self._lock:
                fileobj.write(msg2)
            
            
            
            
            
            
            
            
            
            
            
            
        if logger and not screen_only:
            msg2 = nocolor.lstrip('\n')
            lvl = logging.INFO
            if color:
                
                try:
                    lvl = color_to_log_level[color]
                except KeyError:
                    
                    raise AnsibleAssertionError('Invalid color supplied to display: %s' % color)
            
            logger.log(lvl, msg2)
    def v(self, msg, host=None):