juju-introspection.sh is full of bashisms

On a model deployed with Juju 2.2.8, backed by the OpenStack provider.

The application in question is a web app, which runs as an unprivileged user, where interactive shell usage is not normally required. As such the entry in /etc/passwd (passwd(5)) has no command interpreter set; in turn defaulting to /bin/sh which is a symlink to /bin/dash on Ubuntu.

$ juju ssh my-application/0
ubuntu@juju-deadbeef-my-model-1:~$ sudo -u unpriv -i
-sh: 31: /etc/profile.d/juju-introspection.sh: Syntax error: Bad function name
$

This is because Juju places bashisms in /etc/profile.d/juju-introspection.sh which is sourced by all sh(1) compatible shells - as per the top of /etc/profile:
---
# /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
# and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).
---

This can be reproduced by simply adding a user with a shell set to dash

ubuntu@juju-deadbeef-my-model-1:~$ sudo adduser --shell=/bin/sh unpriv
ubuntu@juju-deadbeef-my-model-1:~$ sudo -u unpriv -i

Or the file could be made sh(1) compatible; the problem is with hyphens in function names.

e.g. https://github.com/juju/juju/blob/1cac709aab13075c1b7ffadc75359d7594236c74/worker/introspection/script.go#L68