Pyjectify

Stable release
- add linting & formatting
- improve documentation
- internal changes to improve consistency & various fixes: some function names may have changed, please refer to the new documentation

**Full Changelog**: https://github.com/Petitoto/pyjectify/compare/v0.7...v1.0

New features
Inject
- Memory loader: added `call_entry_point` parameter to allow loading a module from memory without calling its entry point

Bug fix
Core
- PE: fix `change_base()` (fix relocations parsing and update ImageBase in NT headers)

Others
- Prevent empty memory allocations in injet & pythonlib modules

New features
Core
- Process: added `run_funcs()` to run multiple functions in the same thread (removed `start_join_thread_x64()`)

Bug fix
PythonLib
- Fix PythonLib for Python >= 3.12

New features
Core
- Process: added `start_join_thread_x64()` to get the 64-bits return value of a remote thread

Bug fix
PythonLib
- Fix PythonLib module for Python 3.6-3.9 (still does not work with Python >= 3.12)

Improvements
Core
- Process: `join_thread()` now returns integer instead of ctypes.c_ulong

Bug fix
Syscall
- Fix x86 direct syscalls

Improvements
- Remove ctypes wintypes in core
- ApiSetSchema: use VirtualSize instead of SizeOfRawData

Improvements
Core
- move injectorx86, injectorwow64, windowsx86 from `pyjectify.windows.core.process` to `pyjectify.windows` (named respectively x86, wow64, windowsx86)

PE
- PE are automatically mapped to memory at initialization
- PyJectify automatically detects if a PE is from raw file or if it's already mapped (removed the `mapped` parameter)
- PyJectify automatically parse imports and exports at initialization, unless we specify to PyJectify that we try to parse only PE headers (removed `parse_imports()` and `parse_exports()` public method & added `headers_only` parameter)
- sections now use VirtualSize instead of SizeOfRawData

Inject
- improved injection without headers (do not copy them instead of filling the memory range with null bytes)
- allow to use a random address instead of the base address for memory loader, using the new `prefer_base_addr` parameter