feat: add content and peer routing progress events

[achingbrain]

These are added as optional generics so this change should be non-breaking.

Refs: libp2p/js-libp2p#1652

[SgtPooki]

you should add generics to the extends ProgressEvent in order to appropriately populate progressEvent or else users won't be able to customize their data since it's always going to be set to ProgressEvent<any, unknown>

e.g.

Suggested change

	export interface Libp2p<
	FindPeerProgressEvents extends ProgressEvent = ProgressEvent,
	GetClosestPeersProgressEvents extends ProgressEvent = ProgressEvent,
	ProvideProgressEvents extends ProgressEvent = ProgressEvent,
	FindProvidersProgressEvents extends ProgressEvent = ProgressEvent,
	PutProgressEvents extends ProgressEvent = ProgressEvent,
	GetProgressEvents extends ProgressEvent = ProgressEvent
	> extends Startable, EventEmitter<Libp2pEvents> {
	export interface Libp2p<
	FindPeerT extends string = any, FindPeerD = unknown,
	GetClosestPeersT extends string = any, GetClosestPeersD = unknown,
	ProvideT extends string = any, ProvideD = unknown,
	FindProvidersT extends string = any, FindProvidersD = unknown,
	PutT extends string = any, PutD = unknown,
	GetT extends string = any, GetD = unknown,
	> extends Startable, EventEmitter<Libp2pEvents> {

this can obviously be improved, but without piping the generics through, you will lock types to any and unknown, and aren't getting much benefit

[SgtPooki]

Suggested change

	peerRouting: PeerRouting<FindPeerProgressEvents, GetClosestPeersProgressEvents>
	peerRouting: PeerRouting<ProgressEvent<FindPeerT, FindPeerD>, ProgressEvent<GetClosestPeersT, GetClosestPeersD>>

[SgtPooki]

Suggested change

	contentRouting: ContentRouting<ProvideProgressEvents, FindProvidersProgressEvents, PutProgressEvents, GetProgressEvents>
	contentRouting: ContentRouting<ProgressEvent<ProvideT, ProvideD>, ProgressEvent<FindProvidersT, FindProvidersD>, ProgressEvent<PutT, PutD>, ProgressEvent<GetT, GetD>>

[SgtPooki]

ditto