1153 bytes32 dapi name datafeed

[wkande]

Closes #1153

[github-actions[bot]]

Visit the preview URL for this PR (updated for commit 32c0151):

https://api3-docs--pr1154-1153-bytes32-dapinam-goo1ck57.web.app

_{(expires Fri, 23 Dec 2022 23:01:29 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: d319eb7cbe610768342d5dc1b5cd1f3aed912886}

[wkande]

This PR addresses whether or not a dapiName must be bytes32 encoded before calling the following:

• dataFeedIdToReaderToWhitelistStatus(): See here in preview.
• readerCanReadDataFeed() See here in preview

@bbenligiray - Can you verify the Parameter section of the two docs above?

I discovered that a dapiName such as AVAX/USD must be encoded before calling DapiServer functions like readDataFeedWithDapiName() while writing the guide Calling a dAPI: Using the DapiServer contract and Remix in the new VitePress docs.