Restrict access to MemoryResourceProxy in ManagedMemoryResource

[LittleHuba]

What

Currently ManagedMemoryResource provides a public API to access its underlying MemoryResourceProxy.

This is "bad" as it encourages any user of this ManagedMemoryResource interface to use it, which is NOT intended.

Only our PolymorphicOffsetPtrAllocator shall access it.

How

• Remove the public visibility of getMemoryResourceProxy() in ManagedMemoryResource
• Change the signature of the ctor of PolymorphicOffsetPtrAllocator to get a ManagedMemoryResource
• Only allow PolymorphicOffsetPtrAllocator to call getMemoryResourceProxy()

Estimates for realization

• Effort medium
• No impact on users expected

Category

• Affects Detailed Design

Requirements / Architecture

• Requirements / Architecture are not affected by this change?

[jorgecasal]

I've started implementing the changes required for this issue in the baselibs repository. Before proceeding further, I'd like to clarify the scope:

Question: Should these changes be applied to both the baselibs repository and then subsequently to the communication repository? I want to ensure both repositories are updated consistently.

Any guidance on the order and scope would be appreciated. Thanks!