Eliminate Profile from ContentSettingsUsagesState
ContentSettingsUsagesState only used Profile to get PrefService and HostContentSettingsMap, both of which are outside //chrome. To prepare componentisation of ContentSettingsUsagesState, these are now taken directly by that class on construction, bypassing going through Profile.
Also, |TabSpecificContentSettings::profile_| is removed, because that variable was not used outside the constructor. Profile cannot be removed completely from TSCS yet, because it is used for initialising LocalSharedObjectContainers, getting the HostContentSettingsMap and PrefService. These will be addressed by subsequent CLs (by moving LSOC outside of TSCS, to the ChromeContentSettingsClient; implementing GetHostContentSettingsMap by the client; and probably the same for PrefService).
BUG=387075,387064
Review URL: https://codereview.chromium.org/
688473002
Cr-Commit-Position: refs/heads/master@{#301826}