Text component content types "score, selector, and NBT" do not get resolved for dialogs

Summary:
When you use text component content types like selector, score, and nbt inside a dialog, they are not resolved (i.e., they are displayed literally or not at all). Instead of showing actual player names, positions, or scores, the dialog shows raw component data like @s or nothing.

Steps to reproduce:

1. Create a dialog JSON file with the following contents:

   {
       "type": "minecraft:notice",
       "title": "Dialog Test",
       "body": [
           {
               "type": "minecraft:plain_message",
               "contents": [
                   "All players: ",
                   {
                       "selector": "@a"
                   }
               ]
           },
           {
               "type": "minecraft:plain_message",
               "contents": [
                   "Current player: ",
                   {
                       "selector": "@s"
                   }
               ]
           },
           {
               "type": "minecraft:plain_message",
               "contents": [
                   "All entities: ",
                   {
                       "selector": "@e"
                   }
               ]
           },
           {
               "type": "minecraft:plain_message",
               "contents": [
                   "Your current position: ",
                   {
                       "entity": "@s",
                       "nbt": "Pos"
                   }
               ]
           }
       ]
   }

2. Use one of the following commands to show the dialog:
   a. /dialog show @s namespace:dialog
   b. /execute as @s run dialog show @s namespace:dialog

Expected result:

All players: PlayerA, PlayerB, PlayerC
Current player: PlayerA
All entities: PlayerA, PlayerB, PlayerC, Pig, Cow, Sheep, Zombie
Your current position: [20.0d, 76.0d, 33.0d]

Actual result:

All players: @a
Current player: @s
All entities: @e
Your current position: 

Notes:

• The same selector, nbt, and score components resolve correctly in chat messages, signs, and books.

• This suggests dialogs currently do not support component resolution, which may be unintentional or a missing feature.