docs: update advanced model

[frodehk]

ECALC-531

Have you remembered and considered?

• I have remembered to update documentation
• I have used conventional commits syntax (if you squash, make sure that conventional commit is used)
• I have included the Jira issue ID somewhere in the commit body (ECALC-XXXX)

Why is this pull request needed?

Update examples in eCalc docs to be representative and avoid invalid timesteps. This can be confusing for externals.

What does this pull request change?

• Update Advanced model example with new updated yaml file. Changes in modelling to avoid invalid timesteps. This is aligned with what is being used in courses
• Keep old examples under Course material, for use in training. E.g. to show how to fix invalid timesteps.

Issues related to this change:

https://equinor-ecalc.atlassian.net/browse/ECALC-531?atlOrigin=eyJpIjoiODc3MmU1MmEyNWIzNGVkYTg1YTRmZDBlYjc0OTg4MWYiLCJwIjoiaiJ9

[jsolaas]

Very nice!

I'm assuming the yaml has changed here also? It would be easier to see the changes if moving into files and changes was separated. The renaming of advanced from md to mdx is also not captured, so it looks like a delete and create instead. Not sure how important that is, someone else should probably verify the actual content :)

[frodehk]

Very nice!

I'm assuming the yaml has changed here also? It would be easier to see the changes if moving into files and changes was separated. The renaming of advanced from md to mdx is also not captured, so it looks like a delete and create instead. Not sure how important that is, someone else should probably verify the actual content :)

I agree, it was all in one go. The yaml-content has changed as well, more advanced model. The original yaml (advanced) is now under course content. The simple model in examples and course content is identical for now. The simple model is updated (input file update only) in a separate PR.