* simon/cpfp-frontend: (46 commits)
Bugfix: Don't extend already extended transactions to not override the firstSeen property. fixes#390
Shuffle mempool transactions before saving disk cache. (#398)
Adding missing return after expressjs response.
CPFP support (#395)
Round sat/vB in fee rating tooltip. fixes#364
Add the GNU AGPLv3 logo to About page
Update package.json license tags
Add recommended fee percentile config (#394)
Fix typo in README (#392)
Fix icon for Specter Wallet on About page
Add link to Specter Wallet on our About page
Add link to WARden Portfolio app as Community Integration on About page
Delete MIT+CC license from Terms of Service, add AGPLv3 to About page
Change mempool project license to GNU Affero General Public License v3
Lower volume for sound effects (#385)
Improve grammar, layout, and formatting of Terms of Service page
Display all Project Contributors on About page using GitHub API (#382)
Modify nginx.conf to cache HTML for 10m and static resources for 1h
Proxy /api/v1/contributors from mempool.space, also fix HTTP headers
Add link to Bisq's GitHub repo on About page
...
* CPFP support.
fixes#5fixes#353fixes#360
* Use effectiveFeePerVsize for mempool statistics.
* Renaming endpoint cpfp-info to just cpfp.
* Renaming decended to BestDescendant.
* Updating language file with new strings.
On powerful servers, nodejs automatically sets the limit at 4GB
```
% node -e 'console.log(`node heap limit = ${require("v8").getHeapStatistics().heap_size_limit / (1024 * 1024)} Mb`)'
node heap limit = 4144 Mb
```
On a Raspberry Pi with 8GB RAM, nodejs automatically sets the limit at 1GB
```
% node -e 'console.log(`node heap limit = ${require("v8").getHeapStatistics().heap_size_limit / (1024 * 1024)} Mb`)'
node heap limit = 1048 Mb
```
On a Raspberry Pi with 4GB RAM, nodejs automatically sets the limit at 740MB
```
% node -e 'console.log(`node heap limit = ${require("v8").getHeapStatistics().heap_size_limit / (1024 * 1024)} Mb`)'
node heap limit = 739.4694900512695 Mb
```
After testing with manually setting the limit to 768MB, mempool starts
up fine, but crashes when saving the cache when the mempool is quite
large (over 400MB with custom bitcoin.conf setting).
So it's probably safe to reduce the 4GB limit setting to 2GB for
all devices and and just use the automatically set values, now that the
backend's disk cache memory usage was recently optimized.
However, a new npm script for `npm run start-production` will be added
so we can keep our production mempool.space servers running with a very
large bitcoin.conf mempool
