Sync ephemeral and first party storage cleanup

[goodov]

Changes in this PR:

1. Move cleanup logic from TLDEphemeralLifetime into EphemeralStorageService.
2. Put the actual cleanup calls into BraveEphemeralStorageServiceDelegate which is now located in //brave/browser. This allows us to cleanup //chrome-declared bits.
3. Remove FirstPartyStorageLifetime as TLDEphemeralLifetime now triggers the cleanup event for both EphemeralStorage and ForgetFirstPartyByDefault features.
4. Fix "Shields off" is not working for FBD before page close/reload.

Resolves brave/brave-browser#30090
Resolves brave/brave-browser#30330

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally:
  • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
  • npm run lint, npm run presubmit wiki, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Custom-Headers
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

Per discussion via https://bravesoftware.slack.com/archives/CHGKGMHDJ/p1687362687017369?thread_ts=1680615454.570509&cid=CHGKGMHDJ, the test plan for this one is:

1. Test cases 1-9 of Enable BraveForgetFirstPartyStorage on nightly desktop. brave-variations#567 (comment) (general "Forget by default" test cases)
2. Ephemeral storage specific checks as described in [FBD] Synchronize ephemeral and first party storage cleanup event brave-browser#30090 (comment)

[iefremov]

not only "first party" now?