Allow modules to run code during autolinking (to capture unmet implicit dependencies/requirements)

Sometimes a community module will have requirements for the app to consume it successfully.
For example:

• the react-native-print module requires that the app define a XAML Canvas element named RNPrintCanvas.
• similarly, use of inking will require the app to set IsPerspectiveEnabled=false
• C# modules require C++ apps to add the consumecsharpmodules property (this already works automatically)

In the case of react-native-print, this is documented in the module's readme, but it would be good if there was a way for the module to express requirements or even run some JS during autolink to either (in pri order):

1. print a message explaining module requirements on the app
2. check whether the condition is satisfied and if not print a message
3. check the condition and fix it for the user

The issue does not name files or tests. Start by locating the autolinking entry point and how modules currently express requirements; compare the react-native-print, inking, and consume-csharp-modules cases. Define an agreed mechanism for reporting, checking, or fixing requirements, then validate it against those examples.