Distinguish L1/F2/F4 and let F2 program

Conflicts:
	src/stlink-common.c
Solved by propagating Karl's name change

Verify F2 and F4 by using a decent block size

Remove all project files from stlink.

The project is made with Makefiles, so while the project files provided some convenience to some people, they were not in any
way portable or maintained.  Removing them also allows other people to keep their own versions without having to deal with
shared conflicts.

Updated gitignore to reflec this.

    monitor reset     -- reset the core
    monitor resume    -- get the core running but don't stop gdb executing commands
    monitor halt      -- halt the core

Update documentation

Unify chip id names, fix warnings

Eliminates build warnings.

Flag more duplicate variables that need to be removed/combined

Fixes around F4

Use pkg-config to find libusb

CoreIF for F2/F4 is not different, use CPUID to distinguish. F4 errata seems to give wrong workaround

Allow to write to ram and start loaded programs. 

that case. Report advance in half-word writing. Setting stack and PC give
access error so automatic start fails too and hardware needs to be hard-reset
to start

by consecutive page erase
Allow to erase the device with the flash

SP value and the Program counter with the reset value from the Vector
table. Then run reset function

behaviour with L1 and F2

Conflicts:
	gdbserver/Makefile