Convert SetModeledMethodsMessage to include multiple modeled methods

[robertbrignull]

Converts SetModeledMethodsMessage to include multiple modeled methods and pushes that change throughout the model editor. This means it's now possible to view multiple methods, though it's not yet possible to edit them and save the changes.

This can be tested by manually editing a model file to give multiple modelings for the same method.

Checklist

• CHANGELOG.md has been updated to incorporate all user visible changes made by this pull request.
• Issues have been created for any UI or other user-facing changes made by this pull request.
• [Maintainers only] If this pull request makes user-facing changes that require documentation changes, open a corresponding docs pull request in the github/codeql repo and add the ready-for-doc-review label there.

[koesie10]

Is there a specific reason for using modeledMethodsMap here, while we're using modeledMethods everywhere else?

[robertbrignull]

My intention was to change all instances of things with the type Record<string, ModeledMethod[]> in the model editor webview to modeledMethodsMap, so they're all consistent. That way we aren't calling the data modeledMethods in one component, but then passing it to another component where we call the same data modeledMethodsMap and modeledMethods has a different meaning.

Do you think we should just call it modeledMethods unless we also happen to need objects of type ModeledMethod[] in the same scope?

I didn't spot that my automated renaming had renamed the fields in the type but not when they're used in the component. So we have modeledMethodsMap: modeledMethods when we get the value from the props. I'll fix that because I think that's definitely unhelpful, regardless of the decision above.

[koesie10]

That makes sense, I think the modeledMethodsMap: modeledMethods was just confusing to me.