refactor(Electromagnetism): replace fieldStrengthMatrix with index-evaluation components

[zhikaip]

First of two PRs for the TODOs in Electromagnetism/Kinematics/FieldStrength.lean; the
follow-up fieldstrength_refactor removes the basis-representation lemmas.

Changes

• Components of the field strength are accessed as toField {A.toFieldStrength x | [μ] [ν]}ᵀ
  everywhere. fieldStrengthMatrix and its API are removed, and every lemma stated with it is
  restated in eval form, with fieldStrengthMatrix ↦ toFieldStrength_eval in the name.
• Two new lemmas, toFieldStrength_eval_eq_tensor_basis_repr and
  toFieldStrength_tensor_basis_repr_eq_eval, bridge eval components and the coefficients in
  Tensor.basis, the tensor library's canonical basis. They replace the role of the
  fieldStrengthMatrix bridge lemmas: KineticTerm expands F_{μν}F^{μν} as a sum over
  Tensor.basis coefficients and needs to turn each coefficient into a component, and
  antisymmetry, additivity and homogeneity of toFieldStrength are derived from their
  component versions through the same bridge.
• Tensors/Elab.lean: the bracket index syntax accepts a term instead of an ident, so
  concrete components such as [Sum.inl 0] [Sum.inr i] can be written. Existing uses are
  unaffected.
• Four files gain attribute [-simp] Fin.succAbove_zero (MagneticField, Boosts, KineticTerm,
  Hamiltonian); each fails without it.
• canonicalMomentum_eq is reproved via Lorentz.Vector.inner_eq_sum, and the two options
  in Vector/MinkowskiProduct.lean are dropped. With feat(Lorentz.Vector): mark Vector and CoVector implicit_reducible, add inner_eq_sum #1610 and fix(Tensors): rank the tensor action above the Tensorial action #1611 no
  respectTransparency option remains in the electromagnetism files.

Why

• Index evaluation is the tensor library's own notation for components; fieldStrengthMatrix
  was a second representation of the same thing with a duplicate API.
• Fin.succAbove_zero: plain simp rewrites Fin.succAbove 0 to Fin.succ inside the
  implicit colour index of evalT, after which no eval lemma matches. The tensor library
  disables it file-locally for the same reason; the attribute does not propagate.

replacements are mostly mechanical and AI seem to do a good job. I checked it to the best of my ability

[github-actions]

Thank you for this pull-request (PR). If this is your first PR, welcome to the community!

Below is what will happen next. Please read carefully if you are not familiar with the process. You may open other PRs while this one is being reviewed, and can stack PRs on top of each other, so don't let these steps slow you down.

1. Some automated checks will be run on your PR. You can see the results of these checks at the buttom of your PR page. If any of these checks fail, you will need to fix the issues before your PR can be merged. You can learn more about these here, including how to run them locally, which is sometimes quicker than relying on the GitHub Actions. If you have never had a PR merged before, you may have to wait for a reviewer to manually start these checks (this is for security).

2. A reviewer will look at your PR and may ask you to make changes. This may happen a couple of days after you submit your PR, so you may need to be patient. But it should not be longer than that - if it is please bring it to the attention of the community on the Zulip. The level of review will depend on where your PR is submitted. If it is submitted to ./Physlib or ./QuantumInfo, the review will be more thorough than if it is submitted to ./PhyslibAlpha. You can find out more about what the review process is looking for in our review guidelines. If a reviewer adds an awaiting-author label to your PR, address the review comments, then please remove that label by adding a comment with -awaiting-author. This helps us keep track of reviews.

3. The reviewer will either approve your PR, or request more changes (in which case we return to step 2). Once your PR is approved, it will be merged by a maintainer, this should happen shortly after approval, though you may get more comments at this stage.

Tip: The easiest way to get have a fast review is to submit a PR that is small and self-contained, and has clear documentation explaining why things are the way they are in your chages.

If you have any problems or questions, please reach out to the community on the Zulip.

[zhikaip]

Btw I think toField is extremely confusing with all the field strengths EM fields etc. flying around, I'm thinking of changing it to something like toScalar. I can do that in a follow up PR if you agree

[jstoobysmith]

I think this would make sense. Sorry am at a conference, so haven't had time to look at this properly yet.