google_chrome_profiles: add path column

[slai]

There is currently no column that can be used to link rows returned by the google_chrome_profiles table with the rows returned by the OSQuery built-in chrome_extensions table. This is useful for determining the email, and therefore the Google Account, associated with the profile the extension is installed in, which can be used as a proxy for whether the extension was installed in a work or non-work profile.

This PR adds a path column to the google_chrome_profiles table. This is the path to the profile's directory, and should match profile_path column in the chrome_extensions table, allowing these two tables to be joined together. It does this by pulling out the profile's directory name from the same dictionary used to get the existing data, combines it with the Chrome user data directory path, and finally checks that it exists before returning it. It is possible for this column to be empty, if for whatever reason, the computed path does not exist.

osquery> select * from google_chrome_profiles;
+----------+------------------------+------------------+-----------+-----------------------------------------------------------------+
| username | email                  | name             | ephemeral | path                                                            |
+----------+------------------------+------------------+-----------+-----------------------------------------------------------------+
| user1    | [email protected] | test.example.com | 0         | /Users/user/Library/Application Support/Google/Chrome/Default   |
| user2    | [email protected]      | example.com      | 0         | /Users/user/Library/Application Support/Google/Chrome/Profile 1 |
+----------+------------------------+------------------+-----------+-----------------------------------------------------------------+