New Markdown Examples lack delimiter and padding

[jdhitsolutions]

Steps to reproduce

Take any command that does not have comment based help. I created a tester

function Test-Me {
[cmdletbinding(SupportsShouldProcess)]
Param([string]$Name,[int32]$Size)
$name
$size
}

Then run New-MarkdownHelp for the command.

Expected behavior

I'm expecting an example heading like this:

-------------------------- EXAMPLE 1 --------------------------

Actual behavior

Example 1

Environment data

v0.7.0

[vors]

That's an interesting one.
These delimiters are coming from the actual title in the maml-xmls.
In the core cmdlets, help consistently has them, but in other doesn't.
So it's more of the convention than the standard.

Also see #119 for the same discussion

[vors]

I'm leaning toward stripping delimiters from generated markdown and maybe adding them to maml.
There is no reason to have this delimiters in markdown, because headers already makes a section. Also it would help get a consistent view.

[jdhitsolutions]

As long as the generated MAML has the right example headers I'd be fine with that.

[vors]

Also @cormacpayne pointed out that generated examples don't have extra padding line between them.
This is fixed per 15d62cb

[cormacpayne]

@vors since example headers already create sections in markdown, I like the idea of keeping it "clean" and avoiding delimiters for markdown. However, I think that delimiters will look much better for MAML than a couple extra new lines after each example because it will clearly show when the next example starts.

[vors]

Closing as duplicate of #119