Core: declare scss exports in package

[RasmusKjeldgaard]

Which issue does this PR close?

This PR closes an issue with missing scss exports from our core package, resulting in the following error when compiling the designsystem package in projects:

What is the new behavior?

The package exports field in the badge as web comp PR does not include the utils and global_styles scss partials that were previously exported by default.

They are now added as explicit exports.

Does this PR introduce a breaking change?

• Yes
• No

Are there any additional context?

Checklist:

The following tasks should be carried out in sequence in order to follow the process of contributing correctly.

Reminders

• Make sure you have implemented tests following the guidelines in: "The good: Test".
• Make sure you have updated the cookbook with examples and showcases (for bug fixes, enhancements & new components).

Review

• Determine if your changes are a fix, feature or breaking-change, and add the matching label to your PR. If it is tooling, dependency updates or similar, add ignore-for-release.
• Do a self-review.
• Request that the changes are code-reviewed
• Request that the changes are UX reviewed (only necessary if your PR introduces visual changes)

When the pull request has been approved it will be merged to develop by Team Kirby.

[RasmusKjeldgaard]

Could also be wildcard export to avoid an error in the future, but that would mean we expose all our scss partials as part of our public package, so that would probably be a bit much 🤔

"./scss/*": {
  "sass": "./scss/_*.scss" 
},

[jakobe]

Yes, let's keep it as explicit exports 👍🏻