chore: apply namespace pattern for component props (part 8)

[kurtdoherty]

Context

• Some components currently export their prop interfaces, while others do not. This leads to an inconsistent experience for consumers.
• Further, when exporting component props via a separate export to the component itself, this forces consumers to have two separate imports, one for the component and another for the component's props. This does provide any improvement over the use of React's ComponentProps.
• To provide a consistent approach, and to help consumers avoid needing to separately import component props, the following pattern will be applied to all core components:

export namespace MyComponent {
  export Props extends ... {
    ...
  }
}

export function MyComponent(props: MyComponent.Props) {
  ...
}

This way, when consumers import MyComponent, they will automatically have access to its prop interface via MyComponent.Props.

Past PRs include:

• chore: apply namespace pattern for component props (part 1) #766
• chore: apply namespace pattern for component props (part 2) #767
• chore: apply namespace pattern for component props (part 3) #768
• chore: apply namespace pattern for component props (part 4) #769
• chore: apply namespace pattern for component props (part 5) #770
• chore: apply namespace pattern for component props (part 6) #771
• chore: apply namespace pattern for component props (part 7) #772

This PR

Applies this namespace pattern for component props to the last group of components:

• EmptyData subcomponents (these were missed originally)
• CSSContainerQuery
• MatchMedia
• Popover

Also documents the interface pattern in a new guidelines/interface-pattern.md file.

[rpt-uk-github]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

✅ code/snyk check is complete. No issues have been found. (View Details)

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 7152bd11	✅ 92.16%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (7152bd1)	Report Missing	Report Missing	Report Missing
Head commit (e711751)	9269	8575	92.51%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#773)	51	47	92.16%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩