SA1629 code fix sometimes inserts periods just before last character

SA1629 will flag docs such as these as needing to end with a period:

        /// <typeparam name="S">The service interface to retrieve</typeparam>
        /// <param name="provider">The IServiceProvider implementation</param>
        /// <returns>A reference to the service</returns>

The (bulk) code fix provider produced this:

        /// <typeparam name="S">The service interface to retriev.e</typeparam>
        /// <param name="provider">The IServiceProvider implementation.</param>
        /// <returns>A reference to the servic.e</returns>

Note this doesn’t always repro. When I undo just a few lines to their period-less state and reapply the code fix, the period goes to the right place. It only happens when there are a massive number (possibly hundreds) of fixes applied in bulk.

[sharwell]

@AArnott In the last image (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/issues/2957#issuecomment-657241850), the code fix is correct. The <code> element designates a new paragraph. The equivalent inline element is <c>. DotNetAnalyzers/DocumentationAnalyzers contains analyzers which should detect this case.

[AArnott]

In fact it can be in the middle of a paragraph!