Feature: Spoolman Widget

[fgeck]

Proposed change

Adds a Spoolman widget. Each spool will be rendered into a dedicated <Block> showing the filament name and remaining filament in %.

Widget:

Spoolman:

Closes #3958

Type of change

• New service widget

Checklist:

• If applicable, I have added corresponding documentation changes.
• If applicable, I have reviewed the feature and / or service widget guidelines.
• I have checked that all code style checks pass using pre-commit hooks and linting checks.

[shamoon]

Works great. A couple things, and this needs a re-base.

[shamoon]

Suggested change

	Keep track of your inventory of 3D-printer filament spools.
	Spoolman is a self-hosted web service designed to help you efficiently manage your 3D printer filament spools and monitor their usage. It acts as a centralized database that seamlessly integrates with popular 3D printing software like OctoPrint and Klipper/Moonraker. When connected, it automatically updates spool weights as printing progresses, giving you real-time insights into filament usage.

[shamoon]

Suggested change

	if (spoolData.length === 0) {
	return (
	<Container service={service}>
	<Block label="spoolman.noSpools" />
	</Container>
	);
	}
	if (spoolData.length > 4) spoolData = spoolData.slice(0, 4);

1. I would handle the no spools case (need to add entry to common.json)
2. We dont allow more than 4 blocks, as noted in the guidelines. So up to you how to handle it, at minimum just slice the 4, or you can change the widget in that case (e.g. show a block with total, some other info, etc)

[fgeck]

started incorporating your feedback yesterday.
Need to test and will push again in the upcoming days.

[fgeck]

Finally again ready for review @shamoon

I added an option to filter spools by their id.

Spoolman:

Config:

widget:
          type: spoolman
          url: https://spoolsman.io
          spoolIds:
            - 2
            - 5       # does not exist, but is allowed

Result in homepage:

Ps.:
I hope this will be a squash merge as the commit history of my branch is quite messy.