Customize this page banner shows up when it shouldn't

What does this MR do?

1. We need to hide the banner on / when it is not on the default setting of projects(even if they haven't dismissed the banner as this would signify a change from the default and the user knows about the feature)
2. Hide the banner if the user has navigated directly to /dashboard/projects and hasn't dismissed the banner(should only be valid to show on /)

How to reproduce in GDK

1. Register as a new user.
2. Navigate to /dashboard/projects (http://127.0.0.1:3000/dashboard/projects) or click on menu and select 'your projects'
3. Validate Do you want to customize this page? is not shown.
4. Navigate to / (http://127.0.0.1:3000/) or click GitLab logo in nav bar.
5. Validate Do you want to customize this page? is shown.
6. Navigate to http://127.0.0.1:3000/-/profile/preferences or click user dropdown and select Preferences
7. Set Homepage content to something other than the default and save changes.
8. Navigate to / (http://127.0.0.1:3000/) or click GitLab logo in nav bar.
9. Validate Do you want to customize this page? is not shown.

Screenshots (strongly suggested)

See screenshots from original MR

Does this MR meet the acceptance criteria?

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.
• I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #333711