Create pulumi container

[jemrobinson]

✅ Checklist

• You have given your pull request a meaningful title (e.g. Enable foobar integration rather than 515 foobar).
• You are targeting the appropriate branch. If you're not certain which one this is, it should be develop.
• Your branch is up-to-date with the target branch (it probably was when you started, but it may have changed since then).
• You have marked this pull request as a draft and added '[WIP]' to the title if needed (if you're not yet ready to merge).
• You have formatted your code using appropriate automated tools (for example ./tests/AutoFormat_Powershell.ps1 -TargetPath <path to file or directory> for Powershell).

⤴️ Summary

Ensure that dsh context create also creates the pulumi storage container

🌂 Related issues

Closes #1710

🔬 Tests

Tested on fresh deployment

[JimMadge]

LGTM 👍.

I had to look around the code a bit because I couldn't recall exactly what I had done.

I remember thinking it is a bit odd to import things from the config classes in "context" space because you should create the context before a config.

But these are hardcoded values, so if they belong most naturally in the config I think that is fine. At least, not a bug or priority to move.

[jemrobinson]

Agreed that this should probably live in the Context class but I noticed you already had it as part of ConfigSectionPulumi. I'll leave it up to you whether to fix this now or merge this PR as-is.

[JimMadge]

I'm not really sure. From a "structure of the program" perspective, it would neatly fit in the Context. I think I might have convinced myself it didn't conceptually fit there as the context doesn't really know about Pulumi. However, in the case of the name of the storage account that is part of the context, it totally does.

Added to an existing Issue #1689.