feat!: harmonize service account binding

[aslafy-z]

Closes #320
Closes #361

• BREAKING: Rename rbac.serviceAccount.enabled field to rbac.serviceAccount.create.

• Fix inconsistencies in serviceAccount binding across CronJob, Job, and Deployment templates by introducing a new application.serviceAccountName template:

  rbac.serviceAccount.create	rbac.serviceAccount.name	result
  true	""	(include "application.name" .)
  true	"foo"	"foo"
  false	""	"default"
  false	"bar"	"bar"

• Add field automountServiceAccountToken in pod specs controlled by rbac.enabled.

• Document missing Role and RoleBinding rbac.annotations and rbac.additionalLabels fields.

[d3adb5]

Left a few comments. I like the idea of adding a semantic value like this, but I feel the way it currently is introduces more confusion than clarity. I expanded upon this in one of the threads I opened below.

[d3adb5]

Final set of comments, I promise. Reminder to add a unit test for it if you do take the suggestion. Otherwise, LGTM.

[rasheedamir]

@aslafy-z lets finalize and get this merged

[aslafy-z]

@karl-johan-grahn @d3adb5 Can you please give a look? Thank you!

[karl-johan-grahn]

@aslafy-z Can you please resolve the conflicts?

[rasheedamir]

@d3adb5 can you plz review it again and approve it?

[d3adb5]

LGTM! Sorry for the delay in coming back to this.

[d3adb5]

Do make sure to do a major version bump afterwards!

[aslafy-z]

@rasheedamir @karl-johan-grahn Can you please also review? This PR needs a second approval.
@d3adb5 Thank you for taking some time to look at this PR!