Avoid generating unquoted octal-like strings to avoid parser bugs

[lihaoyi-databricks]

Not every YAML parser distinguishes between unquoted string literals the same way:

• Kubernetes unnecessarily requiring quoting on numeric env vars kubernetes/kubernetes#82296
• https://blog.rowanudell.com/aws-accounts-with-leading-zeros/
• Serverless Transform with YAML removes leading 0 in account number field. aws/serverless-application-model#1469
• AWS Account ID not allowed - Leading 0 account number hashicorp/terraform-provider-aws#15310

This PR forces strings like 088579281390 to be rendered as quoted '088579281390'. While this is not strictly necessary, there are several YAML parsers which mis-handle this kind of output, and so we ensure things are quoted to avoid triggering this edge case.

Added a unit test that on master fails due to generation of non-quoted octal-like strings, and on this PR passes with all strings quoted