The rules are -- if the filter returns str type and the str may contain
non-ascii characters then wrap it to convert to unicode type.  Not
needed if the function already returns unicode type or only returns
ascii characters

Conflicts:
	lib/ansible/runner/filter_plugins/core.py

Fixes #10126

Fixes #10110

non-strings.  Do some value checking in the calling code

Conflicts:
	v2/ansible/inventory/script.py

Conflicts:
	v2/ansible/plugins/shell/sh.py

jinja2 cannot handle byte strs with non-ascii.  So we need to transform potential byte str into unicode type.  This fix is for dynamic inventory.

Fixes #10007

Conflicts:
	v2/ansible/inventory/script.py
	v2/ansible/module_utils/basic.py

Conflicts:
	v2/ansible/plugins/shell/sh.py

Conflicts:
	v2/ansible/plugins/shell/sh.py

Fix quoting of shell parameters used in remote_checksum and add integration test to detect the error

Fixes #682

Conflicts:
	test/integration/roles/test_unarchive/tasks/main.yml
	v2/ansible/plugins/shell/sh.py

Fixes #546

Fix https://github.com/ansible/ansible/issues/9948

not work

Conflicts:
	lib/ansible/modules/core

Fix #9395

Fixes #5865

When they python interpreter is set incorrectly for the machine the file
is being checked for (e.g. for the local or the remote), the error
manifests as a readability or directory missing error which can be very
misleading.

It's up to the module using the set_fs_attributes*/set_mode* methods to
specify the filename of the destination of the symlink if that's really
the file that should be modified.

Half of the fix for:
https://github.com/ansible/ansible-modules-core/issues/778

empty

Listify revert errorhandling

Fixes #9704