PieChart: iterate over component. Introduce size, thickness and padding property

[retrofox]

• Add the padding component property to be able to remove the space.

It's required for us. Otherwise, removing the unneeded padding from the chart will get tricky.
In the following screenshot, the padding around the chart (SVG) affects the Widget layout.

• consistency between PieChart and PieSemiCircleChart
  • Remove width and height properties in favor of size
  • BREAKING CHANGE: Adding the thickness property. Removes innerRadius property

Fixes #

Proposed changes:

• iterate over component PieChart: introduce size, thickness and padding property

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

Use storybook to test the component through its stories

• Confirm that when there is no padding, the SVG element takes the whole size (width):

• Play with the story controls. Confirm it is possible to change size, thickness, and padding properly.

Screen.Recording.2025-01-13.at.11.39.04.AM.mov

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• 🔴 Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[retrofox]

I hope it isn't too late to remove this property 😬

[kangzj]

Good from the Jetpack side at least 😄

[kangzj]

Nice improvements! LGTM 👍