Line numbers support

support bootstrap method coping when using code coping

improve pom

- add `inceptionYear` element, and use it in `copyright bottom`
- add missing version declaration for `maven-gpg-plugin`
  more stable build and fix related warning message
- add `maven-enforcer-plugin`
  more straightforward error message when `maven`/`java` version is not satisfied

polish pom format

- reorder pom elements
  - sort `GAV` elements together
  - bring user concerned info(e.g. licenses) forward
  - bring dev concerned basic info(e.g. dependencies) before profiles
- use `https` instead of `http` for URLs
- change whitespace tabs to spaces for consistency

add `.editorconfig`

ease the view and edit settings of the editor/IDE

more info see https://editorconfig.org/

Fix bytecode compatible back to 52(JDK8)

This project need JDK 11 to compile, but target to JDK 8.

IDEA need uncheck "use --release" in Preferences |
Build, Execution, Deployment | Compiler | Java Compiler
, to build success.

fix #470

Use current latest org.apache.felix:maven-bundle-plugin:5.1.9

https://github.com/jboss-javassist/javassist/issues/471

Minimal changes make IDEA 2023.2 work out-of-box

Fix insertAuxInitializer may cause inconsistent stack height problem

Update tutorial.html: `javassist.util.HotSwapper`

Correct maven-compiler-plugin JDK version for IDEA import Compiler bytecode version.

Remove JvstTestRoot's constructor, otherwise IDEA cannot show Run icon aside testMethod.
Another way is adding suite() static method to those classes.

Now we can clone and open project with IDEA 2023.2. Debug single test case with IDEA is very useful.

Usually, constructor only load super class's constructor's init params into stack.
After this() or super() called, stack will be empty. If so, we insertAuxInitializer
right after this() or super() can reuse max stack size if it enough.

But, there is some weird class out there, their constructors load all in-constructor
init field value into stack before this() or super() call. In this case,
after this() or super() call, stack is not empty, even maybe full.

In summary, insertAuxInitializer should increase MaxStack anyway.

The code path is fixed.

Remove DUP check in TransformNewClass

Fix issue in no-standard [new] instruction replace

Fix MemberResolver.lookupMethod bug when super class has more precise…

DUP usually come after NEW, but not necessary.

#453

When onlyExact=false and super class have a more precise match,
it should not return with current class's maybe result.

New added testSuperCall reveals the problem.

fixes Issue 462 (In Java21, the ConstPool API throws NPE for MethodParameters attributes without parameter names)

A standard *new* construct bytecode will generate like:

```
new okhttp3/OkHttpClient
dup
invokespecial okhttp3/OkHttpClient <init> ()V
astore 1
```

but a few part of compiler will generate no-standard bytecode like:

```
new okhttp3/OkHttpClient
dup
astore 1
invokespecial okhttp3/OkHttpClient <init> ()V
```
which will cause javassist build stack error.

This commit will fix it

try to fix trivial link error

try to fix trivial link error

Includes Automatic-Module-Name in MANIFEST.MF

the previous commit was wrong.