New version: FiniteMPS v1.5.0

[JuliaRegistrator]

• Registering package: FiniteMPS
• Repository: https://github.com/Qiaoyi-Li/FiniteMPS.jl
• Created by: @Qiaoyi-Li
• Version: v1.5.0
• Commit: c395732de6cfb7a86d0aebf37c9e02c8b54d7911
• Reviewed by: @Qiaoyi-Li
• Reference: Qiaoyi-Li/FiniteMPS.jl@c395732#commitcomment-148174124
• Description: Provide some MPS-based algorithms such as DMRG and TDVP.
• Release notes:

## New Features
### Support the computation of imaginary-time proxy (ITP)
ITP forms like $\langle A(\beta/2) B\rangle_\beta = Z^{-1}{\rm Tr}\\{e^{-\beta H/2} A e^{-\beta H/2} B\\}$, which can be directly obtained with the thermal density operator $e^{-\beta H/2}$ represented as MPO. We provide the following interfaces for users.

- A concrete type `ImagTimeProxyGraph` to describe the terms to be calculated.
- `addITP2!` and `addITP4!` for adding terms like $\langle A_i(\beta/2) B_j\rangle_\beta$  and $\langle A_i(\beta/2) B_j(\beta/2) C_k D_l \rangle_\beta$, respectively.
- `merge!` to compress the graph partially.
- `calITP!` for in-place calculation. 

Detailed usage please see the documentation via `?` in REPL.

### Example
The following shows a sample code for the calculation of the single particle Green's function $\langle c_i^\dagger(\beta/2) c_j\rangle_\beta$ with $U_1\times SU_2$ symmetry.
```julia
G = ImagTimeProxyGraph(L)
for i in 1:L, j in i:L
    addITP2!(G, U1SU2Fermion.FdagF, (i, j), (:Fdag, :F); Z=U1SU2Fermion.Z)
end
merge!(G)
calITP!(G, rho)
```
where `rho` is a length-`L` MPO that represents $Z^{-1/2}e^{-\beta H/2}$. After this, the value of $\langle c_i^\dagger(\beta/2) c_j\rangle_\beta$ is stored at
```julia
G.Refs["FdagF"][(i, j)][]
```

There may exist bugs that have not yet been discovered, please check carefully with the results.

## Other changes
- Update dependent packages such as `TensorKit.jl` and `KrylovKit.jl`.

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. AutoMerge Guidelines are all met! ✅

Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round.

2. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.