customization panel should not be open by default on New Tab page

[karenkliu]

Description

Currently, the customization panel is open by default on New Tab page.

Fix this so that the panel is not open by default.

[imptrx]

The first time someone opens NTP the settings menu would be off. I believe the current behavior you are experiencing is:

• user visit NTP
• the settings menu is turned on by the user
• the user doesn't close it via clicking outside or button toggle

If that's the case, the menu would persist over to the next NTP session.
If we don't want to preserve the last session of the settings menu, that would be a different issue altogether, could we confirm if that's the case?

[rebron]

@imptrx That's the case. Don't preserve the last session of the settings menu when user opens up a new tab page. Should always show closed when creating a new tab page.

[imptrx]

Test Plan:

1. Open new tabs page
2. Open customization menu at the bottom right corner
3. Open another NTP and assert customization menu is closed
4. Close browser with customization menu open; NTP on a fresh browser instance should be closed

[petemill]

@imptrx I suggest you use component state and not redux state for the openness of the menu, or just delete the redux property when the redux state is saved to localStorage

[imptrx]

@imptrx I suggest you use component state and not redux state for the openness of the menu, or just delete the redux property when the redux state is saved to localStorage

@petemill I currently have a "close menu" action attached to NTP component mount but I'll probably move that logic out of redux as you suggest 👍

[GeetaSarvadnya]

Verification passed on

Brave	0.69.115 Chromium: 76.0.3809.100 (Official Build) beta (64-bit)
Revision	ed9d447d30203dc5069e540f05079e493fc1c132-refs/branch-heads/3809@{#990}
OS	Windows 10 OS Version 1803 (Build 17134.523)

• Verified the test plan from Make NTP setting menu keyboard accessible  brave-core#2814

Verification passed on

Brave	0.69.116 Chromium: 76.0.3809.100 (Official Build) beta (64-bit)
Revision	ed9d447d30203dc5069e540f05079e493fc1c132-refs/branch-heads/3809@{#990}
OS	Ubuntu 18.04 LTS

• Verified the test plan from Make NTP setting menu keyboard accessible  brave-core#2814
• Verified the test plan from customization panel should not be open by default on New Tab page #5199 (comment)
• Made sure that upon changing the setting on one NTP, it is propagated to other NTPs.

Verification PASSED on macOS 10.14.6 x64 using the following build:

Brave	0.69.121 Chromium: 76.0.3809.132 (Official Build) beta (64-bit)
Revision	fd1acc410994a7a68ac25bc77513d443f3130860-refs/branch-heads/3809@{#1035}
OS	Mac OS X

• Went through and verified the outlined test plan via customization panel should not be open by default on New Tab page #5199 (comment)
• Made sure that upon changing the setting on one NTP, it is propagated to other NTPs.