cache hit when cache generated from a different profile

[John Johansen]

AppArmor policy caching does not correctly track which profile generated the cache entry, nor the contents of the profile used to generate the entry which can result in a false positive hit

To replicate
take two versions of the same profile (with some variation) with the same basename, load the one and then the other

apparmor_parser -kWr ./usr.lib.colord
Cache miss: ./usr.lib.colord

apparmor_parser -kWr /etc/apparmor.d/usr.lib.colord
Cache hit: /etc/apparmor.d/cache/usr.lib.colord

the second profile is different and should result in a cache miss, but because the apparmor_parser is only testing based on the basename of the file and the timestamps involved, the cache is hit and the first version of the profile is used instead of compiling and loading the new version.