This opens up other scenarios for specific constants we don't want
behind a Constants propery (i.e ThisAssembly.Git, see #69).

A small refactoring of the targets with a new PrepareConstants
will also make it easier for extenders to run before we do our
conversion to AdditionalFiles, to keep the extended items clean
even when they need to run before/after certain targets.

* Move Path Sanitizer code to common .cs file

* Update ThisAssembly.Resources to use common .cs file code

* Test Sanitization Code

* Fix more path name issues

Closes #167

* Handle rare corner case ("/0/0/abc.csv")

Bumps [PolySharp](https://github.com/Sergio0694/PolySharp) from 1.8.3 to 1.12.1.
- [Release notes](https://github.com/Sergio0694/PolySharp/releases)
- [Commits](Sergio0694/PolySharp@1.8.3...1.12.1)

---
updated-dependencies:
- dependency-name: PolySharp
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

# devlooped/oss

- Fix incremental build issue with package files and doc file devlooped/oss@96b6773

…y.Constants

This new package is just targets that leverage git-based SourceLink
packages (which must be installed separately since there is a variety)
to populate source control information, turn it into constants that then
the ThisAssembly.Constants package surfaces in a standard manner.

We do not force run of source control queries in design-time builds,
unless the user forces it. This keeps the performance characteristics
of SourceLink, at the expense of a slightly confusing user experience
where intellisense might show the properties as empty all the time
while in fact it's just during design-time.

Closes #69

No need to show values since at design-time, they will look empty anwyays.