Support reload vs restart

BIND doesn't need to restart, and causes service disturbance when restarted vs reloaded (i.e. if something breaks in a restart, you're down, however in a reload if you break, you just don't load the change but at least you're still up).

1. Add (I've done this in my own branch thus far...)

action :reload do
  service new_resource.service_name do
    action :reload
  end
end

2. Address when to reload vs restart. Zone changes should be a reload. Zone additions and deletions can technically also be an rndc command, specifically rndc reconfig, however it won't reload existing zones (you still need rndc reload. We can also be more targeted on the reload to do rndc reload <ZONE> and if this cookbook is supporting views (not sure that it is), then we'd add the view context to resulting in rndc reload <ZONE> <VIEW>. I haven't made updates for this but as referenced above, I've done number 1.

Start by locating the bind cookbook's service action and the zone change handling described in the issue. Confirm how reload and restart are currently selected, then determine the required behavior for zone changes, additions, and deletions, including whether views are supported. Done means the reload action and reload-versus-restart behavior are implemented and verified against the cookbook's existing checks.