Remove unneeded margin: 0 override for Notice component consumer

[ecgan]

What?

Closes issue #55279.

In this PR, we remove the margin: 0 override for Notice component in the Gutenberg repo.

Why?

This is because the custom margin for the Notice component has been removed in PR #54800, so we don't need to have these margin: 0 override anymore.

How?

Testing Instructions

Important note: I have not figured out a way to test my changes in the code repo in my local machine. I couldn't find documentation on this in the repo. If someone could tell me how to do this in the comment below, that would be great.

1. Check out this PR.
2. Run npm install.
3. Run npm run build. It should complete successfully without any errors.

Testing Instructions for Keyboard

Screenshots or screencast

[draganescu]

I have not figured out a way to test my changes in the code repo in my local machine

Hi @ecgan - you can find plenty of documentation about setting up your local development environment in the developer documentation

[t-hamano]

Thanks for the PR! These changes make sense to me, but we would also need to remove the import statements for the scss files that were removed by this PR.

gutenberg/packages/block-editor/src/style.scss

Line 27 in 55b4e9b

@import "./components/contrast-checker/style.scss";

[ecgan]

I have not figured out a way to test my changes in the code repo in my local machine

Hi @ecgan - you can find plenty of documentation about setting up your local development environment in the developer documentation

Hi @draganescu , thanks for the link, but the problem isn't really about setting up my local development environment. It's more about how to test the changes introduced in this PR, and hence how to write the test instructions for this PR. I do not know how I can view and test the CSS code change (for before and after code change).

[ecgan]

These changes make sense to me, but we would also need to remove the import statements for the scss files that were removed by this PR.

@t-hamano , thanks, it slipped my mind. I noticed it caused errors in GitHub Actions. I have fixed it in e17866f (#57794). I have also made sure that npm build works fine in my machine, and updated the test instructions in this PR to mention that.

[t-hamano]

@ecgan Thank you for updating the PR. Is it possible to rebase this PR with the latest trunk branch to merge this PR? Because currently the unit test is failing, but the latest trunk fixes it.

[ecgan]

@t-hamano , thanks for the note. I did a merge in ded5150 (#57794). All checks have passed now.

[t-hamano]

@ecgan Thanks for the update! All GitHub Actions are green, let's merge 👍