RequiredPrivilege should replace weak functions with another mechanism

[mlepage-google]

PR #16327 introduced weak functions MatterGetAccessPrivilegeForReadAttribute (and WriteAttribute, InvokeCommand, ReadEvent).

This is because RequiredPrivilege is built into the DM/IM library, but the underlying data is built per app/example.

Ideally we would have a better mechanism that would not rely upon weak functions, since they can be cumbersome and error prone to ensure the correct ones are linked. We don't want to inadvertently have an artifact using an unexpected implementation of those functions, since they are used to check access control for DM/IM operations.

Probably we should have a "provider" interface and then the artifact can install/configure it at startup.

[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.

[stale]

This stale issue has been automatically closed. Thank you for your contributions.