conda package nbdev 2.3.7 does not install the correct CLI executables for use from terminal, on Windows

I am following up on issue #1120 which was too broad. I had a better look at nbdev on Windows (native) and captured the trial process in a [blog post](https://jmp75.github.io/work-blog/posts/20221007-nbdev-windows). TL;DR version it seems to work well if installed with `pip`, but not if installed as `conda` packages.

## Observations

Installing with `mamba install -n bm -c fastai -c conda-forge nbdev` leads to startup scripts such as C:\Users\abcdef\Miniconda3\envs\bm\Scripts\nbdev_clean containing:

```py
#!C:/Users/abcdef/Miniconda3/envs/bm/bin/python
# -*- coding: utf-8 -*-
import re
import sys
from nbdev.clean import nbdev_clean
if __name__ == '__main__':
sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])
sys.exit(nbdev_clean())
```
if nbdev is installed from pip, we have executables such as C:\Users\abcdef\Miniconda3\envs\bm\Scripts\nbdev_clean.exe and they appear to work as expected.

Note that this seems to be the case for the dependency packages `ghapi` and `nbexec` as well.

## Environment

* OS Windows 10 Enterprise
* Version 21H2
* OS build 19044.2006
* Experience Windows Feature Experience Pack 120.2212.4180.0
* Conda (miniconda for windows)
* conda 22.9.0

Beginne damit, die in issue #1149 beschriebene native Windows-Installation zu reproduzieren: Vergleiche die von `mamba install` erzeugten Terminal-Launcher mit denen von `pip`, und ziehe den verlinkten Blogbeitrag sowie issue #1120 als Kontext heran. Überprüfe die Paketausgaben von `nbdev`, `ghapi` und `nbexec`; als abgeschlossen gilt die Aufgabe, wenn die mit conda installierten Befehle wie bei der pip-Installation funktionierende Windows-Ausführungsdateien bereitstellen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.