docs: inline parsing should honor template location

[kblok]

Having this doc:

### option: Browser.newContext.-inline- = %%-shared-context-params-list-%%

### option: Browser.newContext.proxy = %%-context-option-proxy-%%

### option: Browser.newContext.storageState = %%-js-python-context-option-storage-state-%%

### option: Browser.newContext.storageState = %%-csharp-java-context-option-storage-state-%%

### option: Browser.newContext.storageStatePath = %%-csharp-java-context-option-storage-state-path-%%

The inline elements were being pushed back in the list instead of honoring the position of the template in the main doc.

[avodovnik]

Do we expect many changes from this? Have you checked against the current baseline which files get modified?

[kblok]

Not many changes, @avodovnik. Only in NewContextAsync and NewPageAsync. You can take a look at it here https://github.com/microsoft/playwright-sharp/pull/1316/files#diff-830df37f7e83748f967f8fcbce73a543c3525c745e1f80f998db27992c322a92R184

@yury-s, do you think this could break Java?

[pavelfeldman]

As long as our -inline- are only for the options, it should not break Java/Python!