ResourceRef confusion in operator support

[absoludity]

Summary
While working on #6013, particularly replacing the frontend code with the connect grpc-web client, I've hit a lint type issue because with the previously generated files, the ResourceRef object was apparently interchangeable with the shared/ResourceRef object which was still used for operator support, and included extra fields (filter, namespaced etc.) With the new generated files, the code works fine in tests, but tsc won't allow these two objects to be used interchangeably.

I don't want to risk an unintended change within the large PR that I'm doing, so will instead disable the lint for this item specifically in my PR have extended our custom ResourceRef from the client one, so that I can come back and look at removing our custom one in isolation with a focused PR and proper testing.

Description
The main place this arises in in the OperatorInstance.tsx where the resulting resource refs are collected using an IAppViewResourceRefs:

kubeapps/dashboard/src/components/OperatorInstance/OperatorInstance.tsx

Lines 48 to 56 in e3d4cd5

	let result: IAppViewResourceRefs = {
	ingresses: [],
	deployments: [],
	statefulsets: [],
	daemonsets: [],
	otherResources: [],
	services: [],
	secrets: [],
	};

This interface uses the client ResourceRef class, yet the OperatorInstance code adds the shared/ResourceRef annotated objects, which are not compatible due to the missing methods and constructor etc.

Additional Info

CustomAppView appears to use the extra namespaced field in tests (but doesn't appear to need to) Similarly, Kube.test.ts appears to use namespaced unnecessarily. Need to audit whether any of the extra fields are used elsewhere. The test "updates the state with the CRD resources" fails if using normal resourcerefs here, because of the missing filter, but again, need to audit where this filter field of the ResourceRef is used in the actual code outside tests.

[absoludity]

It wasn't actually a lint error but an actual tsc compile error. So no warning or lint error to suppress. Instead I've updated our internal ResourceRef with the extra fields to be a child (extends) of the client ResourceRef so that they can be used as the same type (polymorphism). I still want to come back to remove our extended version, if possible (ie. if it's no longer being used)..

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.