Implement opt-in merging of elements

[jank324]

I had an issue with the LCLS lattice, where the speed really wasn't great. This was likely due to that lattice having a huge number of elements. However, in my RL environment, I only ever tough a few of them. Most elements remain constant all the time.

I've implemented a new element type that just has a custom transfer map. This can be useful for all kinds of things actually. For my problem in particular, it is possible to take consecutive elements that won't be changed and combine their transfer maps into such an element.

In addition with some other minor optimisations (removing inactive Markers and so on) this gave me around a 20x speedup. I'm currently thinking about whether to also include those optimisations in this PR.

All these optimisations are (currently) opt-in, i.e. you create a new optimised segment by calling a method of the old segment.

[jank324]

Also there is an issue right now that over the LCLS lattice I am not getting exactly the correct Twiss parameters. It's small enough to possibly be a numerical error, but large enough that it might also be a proper error. I am investigating.

[jank324]

Remaining todos for this PR:

• [x] Add convenience function for inactive marker removal
• [x] Add convenience function for removal of inactive zero-length elements
• [x] Add convenience function for replacing inactive long elements with drifts
• [x] Add tests
• [x] Add computation speed optimisation example Notebook
• [x] Remove test Notebook
• [x] Add entry to changelog