Bug: helm namespace scope not respected in telegraf charts

When passing a namespace flag to helm, the namespace is not included in the chart templates for some objects. Result is that telegraf is always deployed to `default` namespace.

Chart version: 1.8.65

Example: only `Role` and `RoleBinding` use the namespace parameter.
```
$ helm template influxdata/telegraf -n MYNS | grep -B5 MYNS
level=WARN msg="unable to find exact version; falling back to closest available version" chart=telegraf requested="" selected=1.8.65
# Source: telegraf/templates/role.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: release-name-telegraf
namespace: MYNS
--
app.kubernetes.io/name: telegraf
app.kubernetes.io/instance: release-name
subjects:
- kind: ServiceAccount
name: release-name-telegraf
namespace: MYNS
```

Start by running the reported `helm template influxdata/telegraf -n MYNS` command and inspect the chart's templates, including `templates/role.yaml`. Compare the rendered namespaces across the objects and identify which templates ignore the namespace parameter. Done means the affected objects render in the requested namespace, with the existing Role and RoleBinding behavior preserved.

Written by the indexing model from the issue text.