Add lineage hash for all levels: `Config`, `Plugin`, `Component`, and `Context`

[dachengx]

The deduced codes and likelihood names are included, so the lineage hash is responsible for a specific simulation(fitting) of Component(Context).

The hash is only available after the deduction of codes(deduce) and it is suggested to run only once per simulation or fitting.

Usage:

config.lineage_hash
plugin.lineage_hash
component.lineage_hash
context.lineage_hash

I am not so sure whether the lineage_hash in this PR is sufficient to track ALL configurations of all levels. Maybe we will come back to it later.

[coveralls]

Pull Request Test Coverage Report for Build 10168924520

Details

• 63 of 73 (86.3%) changed or added relevant lines in 6 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.4%) to 85.18%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
appletree/config.py	17	18	94.44%
appletree/utils.py	9	10	90.0%
appletree/likelihood.py	15	23	65.22%
<!--	Total:	63	73	86.3%	-->

Totals
Change from base Build 10104014836:	0.4%
Covered Lines:	2414
Relevant Lines:	2834

---

💛 - Coveralls