Build EVS manager as a part of the car product

This change modifies car_product/build/car_base.mk to build EVS manager
v1.1 by default.  To do this, this reorganizes EVS selinux policy files
and places them in each component's directories.

And, this change introduces a new build variable, ENABLE_EVS_SAMPLE.
When this variable is set as true, the reference EVS application and EVS
HAL implementation will be built.

Also, this change replaces a few selinux rules with their equivalent
macros.

Bug: 168017200
Test: Build, flash the image, and manually check audit messages on the
      device running in the permissive mode while below executables are
      running:
      - /system/bin/evs_app
      - /system/bin/android.automotive.evs.manager@1.1
      - /vendor/bin/android.hardware.automotive.evs@1.1-sample
Change-Id: Ieffabcba6e05e7b20f0282d1346d77e87553fb6a
19 files changed
tree: b1ab8bcd2398e6c800cae46dc6a50a3bedaa64b9
  1. car-bugreportd/
  2. car-internal-lib/
  3. car-lib/
  4. car-maps-placeholder/
  5. car-systemtest-lib/
  6. car-test-lib/
  7. car-usb-handler/
  8. car_product/
  9. cpp/
  10. evs/
  11. experimental/
  12. FrameworkPackageStubs/
  13. obd2-lib/
  14. packages/
  15. procfs-inspector/
  16. service/
  17. tests/
  18. tools/
  19. user/
  20. vehicle-hal-support-lib/
  21. .clang-format
  22. .gitignore
  23. Android.mk
  24. CleanSpec.mk
  25. CPPLINT.cfg
  26. OWNERS
  27. PREUPLOAD.cfg
  28. README.md
  29. TEST_MAPPING
README.md

Native (C++) code format is required to be compatible with .clang-format file. Run

git clang-format --style=file --extension='h,cpp,cc' HEAD~

Note that clang-format is not desirable for Android java files. Therefore the command line above is limited to specific extensions.