[wip] [feat] Add style overrides and override whitelist

[mrderyk]

CONTEXT

Users need to be able to override certain styles of the search component.

CHANGES

• Add whitelist of CSS styles that can be overridden
• Create type that accepts CSS styles for specific portions of the search component UI
• Apply CSS styles to corresponding elements

[mrderyk]

Added this to remove the noise around building the packages.
We can always build prior to publishing, without including the built files in the repo.

[cjcenizal]

Makes sense! Might be better to extract it into a separate PR to uncouple the changes?

[mrderyk]

These seemed to make the most sense to me, but we can add/remove as we see fit. What this allow-list lets us do is ensure that critical styles (i.e. the ones that maintain the general structure and positioning that we intend for the component) cannot be broken.

[cjcenizal]

Is the intention here to provide consumers with a simpler interface for implementing a coarse-grained customization of the appearance of the search component? For example, simply using the same font-family as the host site/app or applying a color scheme that's consistent with that of the host site/app.

And is the expectation that if the consumer wants finer-grained control over the styles then they'll define those styles as overrides in the host site/app's CSS layer?

[cjcenizal]

I think we should hold off on incrementing version numbers until we're ready for a release. I'd suggest leaving it at 0.0.0 until we're ready for an initial release, which may be 1.0.0 if we're confident in its public use or 0.0.1. if we want to do some internal or limited testing first.

[cjcenizal]

Makes sense! Might be better to extract it into a separate PR to uncouple the changes?