Add convenience bindings in __init__

[ca-scribner]

I liked what @DnPlas did in the training operator where she bound a few commonly used things from the model to local attributes in __init__. Should we add some standard ones to our template? Yes, these are things that are already available (via self.model... etc), but to new people they're hard to find (and sometimes interpret, for example namespace). At a minimum, bindings tend to read better in the code.

I'm thinking something like:

def __init__(...):
  self._name = self.model.app.name
  self._namespace = self.model.name  # Or even better, we put in the template the more robust namespace solution @jnsgruk proposed a few weeks back, I think to handle when something is accidentally deployed into the controller model?
  self._model_name = self.model.name
  # (other things)

[jnsgruk]

I'm not sure about including this in the template itself. Particularly given that not all charms will necessarily use them, and in particular, the variable _namespace makes little sense in the context of a machine charm.... (I accept that the template has containers/pebble stuff in it...)