fix(breadcrumb): component review - TWIG-205

[Joosthe]

PR description

Please drop a few lines about the PR: what it does, how to test it, etc.

QA Checklist

In order to ensure a safe and quick review, please check that your PR follow those guidelines:

• I have put the vanilla component as devDependencies
• I have put the specs package as devDependencies
• I have added the components directly used in the twig file (with include or embed) as dependencies
• My component is listed in @ecl-twig/ec-components's dependencies
• My variables naming follow the guidelines (snake case for twig)
• I have provided tests
• I have provided documentation (for the "notes" tab)
• If my local yarn.lock contains changes, I have committed it
• I have given my PR the proper label (pr: review needed to indicate that I'm done and now waiting for a review ,pr: wip to indicate that I'm actively working on it ...)

[planctus]

@Joosthe, i think we talked about this, the idea in general is that if it's possible, we move what we might have been doing in a story file to pass some data to the component, to the specs (the adapter in this case), so that also when the component is rendered programmatically (js and php) we get the same rendering.
In this case for instance the diff is still showing differences that we can easily and properly fix by applying those information in the adapter instead of doing it in the story.
If there's still lack of clarity about this, please ask about any doubt you may have.

[Joosthe]

Oke i have changed the values will now be loade from the specs

[planctus]

@Joosthe , i pushed a commit to make the diff entirely green, it also contains a simplification of the tests (it all comes from the specs right now), take a look and see if it's good for you ;)