Change/Fix: Include "theme-css/*.scss" files

[alphapapa]

This includes Sass files in the theme-css directory (previously they were only included from the downstream css directory).

To be used in #418.

[netlify]

✅ Deploy Preview for scientific-python-hugo-theme ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	72382e9
🔍 Latest deploy log	https://app.netlify.com/sites/scientific-python-hugo-theme/deploys/65679562fea6e800087e4ce7
😎 Deploy Preview	https://deploy-preview-429--scientific-python-hugo-theme.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 82 Accessibility: 100 Best Practices: 100 SEO: 92 PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[stefanv]

Note the review comment on **/* syntax being supported.

[alphapapa]

Note the review comment on **/* syntax being supported.

@stefanv Thanks, I applied that glob pattern to all the relevant places in this file.

[alphapapa]

@stefanv Using the **/* glob pattern caused Undefined mixin errors which broke the build. I'm not sure what's going on there, but after I reverted those changes in 72382e9, the build succeeded again.

#418 is waiting on this to be merged, so if you'd like me to look into the issues with that glob pattern, I could do that in a separate issue.

[stefanv]

The reason for this indentation is because of the generated HTML—with this change, the generated file with have spaces before the <link> tags.
I'm OK with keeping it as-is, but my emacs also doesn't indent that way by default.
Perhaps you have settings I can adopt?

[alphapapa]

I indented these lines manually for clarity in the source code (the {{- end -}} repeated 3 lines in a row, with different opening lines for each block, is hard to follow). But just let me know how you want this to be done.

[stefanv]

@stefanv Using the **/* glob pattern caused Undefined mixin errors which broke the build. I'm not sure what's going on there, but after I reverted those changes in 72382e9, the build succeeded again.

#418 is waiting on this to be merged, so if you'd like me to look into the issues with that glob pattern, I could do that in a separate issue.

It probably means that we should only load top-level PDST SCSS, which then itself imports deeper down.

[alphapapa]

@stefanv Using the **/* glob pattern caused Undefined mixin errors which broke the build. I'm not sure what's going on there, but after I reverted those changes in 72382e9, the build succeeded again.
#418 is waiting on this to be merged, so if you'd like me to look into the issues with that glob pattern, I could do that in a separate issue.

It probably means that we should only load top-level PDST SCSS, which then itself imports deeper down.

Ok, shall we handle changing the glob patterns in a separate issue then? It also seems like a bit of a design or policy decision, whether to use or allow subdirectories for downstream stylesheet files.

[stefanv]

Thanks, let's get this in so the copy button PR can be rebased.