more vendor services to shutdown critical

- Shutting down these services lead into close call blocked
  ,which can lead into blocking fput of the whole system and
  thus blocking file system umount / shutdown.
- Just keep them during shutdown as long as they do not access /data,
  /persist

bug: 37737296
Test: python packages/services/Car/tools/bootanalyze/bootanalyze.py -r -c packages/services/Car/tools/bootanalyze/config.yaml -n 100 -f -e 11 -w 30 -m boot_fs_shutdown=5000 -v and check if boot_fs_shutdown time exceeds 5 secs.

Change-Id: Ib42b1d840ee861730c82ecde9e08b288d3aae931

init.hardware.rc

@@ -508,6 +508,7 @@ service per_mgr /vendor/bin/pm-service
     user system
     group system
     ioprio rt 4
+    shutdown critical
 
 service per_proxy /vendor/bin/pm-proxy
     class core
@@ -560,6 +561,7 @@ service qseecomd /vendor/bin/qseecomd
    class core
    user root
    group root
+   shutdown critical
 
 service time_daemon /vendor/bin/time_daemon
    class core
@@ -740,6 +742,7 @@ service chre /vendor/bin/chre
     user system
     group system
     socket chre seqpacket 0660 root system
+    shutdown critical
 
 service power_sh /vendor/bin/init.power.sh
     class main