question: rfcs 0212 pick up - list protocol

We are working to implment https://github.com/hyperledger/aries-rfcs/commits/master/features/0212-pickup and have an outstanding PR here https://github.com/hyperledger/aries-framework-go/pull/1926.

I'd like some additional clatiry around the use cases for the `Message Query` / `Message List` as we have not found a need for them in our implementation @dgunseli / @denizgunseli . Mentioning @TelegramSam as we had a brief exhange in chat.

> As I look it, these are protocol level messages that would not have a "user interface" in place to select individual or multiple, message ids. Once the status request is made and the batch satisfied my thought was that would be the end of the interaction, the edge never really have "insight" into it messages waiting at the agent.

I'd propose once we get the PR merged we update 0212 to demonstrated and drop the message query portion from the rfcs, but wanted to raise a discussion first.