Drop component readme files from the monorepo

[jcfranco]

Description

The documentation site has served as the primary documentation source for our components, making these files no longer necessary to keep and maintain. Since Lumina does not generate these readmes, creating them would require additional effort that doesn't seem worth it at this point.

cc @geospatialem @DitwanP @benelan @macandcheese

Which Component

All readme files.

Resources

No response

[driskull]

Maybe in the future we could have something else to tell us the dependencies info.

calcite-design-system/packages/calcite-components/src/components/list/readme.md

Lines 65 to 87 in bcc19be

	## Dependencies
	### Depends on
	- [calcite-scrim](../scrim)
	- [calcite-stack](../stack)
	- [calcite-filter](../filter)
	### Graph
	```mermaid
	graph TD;
	calcite-list --> calcite-scrim
	calcite-list --> calcite-stack
	calcite-list --> calcite-filter
	calcite-scrim --> calcite-loader
	calcite-filter --> calcite-input
	calcite-input --> calcite-progress
	calcite-input --> calcite-icon
	calcite-input --> calcite-input-message
	calcite-input-message --> calcite-icon
	style calcite-list fill:#f9f,stroke:#333,stroke-width:4px
	```

[jcfranco]

We might be able to extract that info from the Vite build. cc @maxpatiiuk

[maxpatiiuk]

you should be able to extract this information from the context._customElementDependencies property.
the property is present in the typings, but marked as private via JSDoc - I can expose it if you need it.
you can get the reference to the Lumina's context object like so, among other ways:

// vite.config.ts
const lumina = useLumina({ ... } );
const context = lumina.context;
export default defineConfig({
  plugins: [lumina],
});