Improve "See gun port definition" link

[SomeTroglodyte]

Formatting and linking

Summary

a) CreatingOutfits has a link "See the gun port definition" which does link to the overall ship page, not the specific definition. It might not be obvious how to achieve anchors without using official markdown headers, but as long as github renders the markdown, it's possible. b) CreatingShips was using a fake footnote using the ¹ character - but footnotes do work in github-rendered markdown. Note I left the footnote text in its original place, but github will render it at the end of the page, with anchor-links to it and back - I'm using one below in this very comment.

Notes

• There's surely other cross-linking in this wiki that could profit from anchors, but I haven't searched for them - in case this technique is acceptable, those are for future PR's.
• Q: The wiki says "parallel" does not apply to turrets but code comments say otherwise - is this a wiki or code issue?
  • e.g. Indicates if this hardpoint disallows converging (guns and the idle position of turrets).
  • I believe 'parallel' will influence turrets if and only if they define an "arc", and prevent shifting the midpoint of that arc same as guns. If I'm right, this tidbit seems to be missing from the wiki.
• Q: The convergence point calculation for non-parallel guns is hinted at in the wiki, but could be more specific - it could show the asin(dx/dy) kind of formula, it could hint that if the convergence point seems off[^1], then the calculated range as displayed in outfitter will be off too - due to projectile acceleration being ignored and so on... Worth some clarification?

[^1]: This led me to investigate in the first place

[warp-core]

The use of a markdown footnote here moves the text from where it currently is to the very bottom of the page. It also changes the colour and size of the text. I don't think that's a good change.

[SomeTroglodyte]

moves the text from where it currently is to the very bottom of the page

Yes, I said so. Given the current position waits until after the current list ends, it looks a little lost and out of context there anyway, and since it has no distinct visual characteristics, it's not easily clear it's meant as a footnote, not a continuation of the text immediately preceding it.

But yes - github's footnotes are a bit dim. All a matter of taste[^1]. And regrettably there is no intermediate option. I can fake a footnote reference and link it, and I can inline a fake footnote that looks mostly like a true footnote with or without the size and color changes - but github forcibly decorates custom href's with user-content and some guid, so those links won't work. Plus, that would be some more massive html injection with reliance on the framework's css not changing - nah.

[^1]: Just vote, I'll revert if y'all wannit. Just adding a space after the current ¹ would already help a bit.

[warp-core]

If we're going to do anything with the footnote, I'd rather it be made not a footnote and included at an appropriate place in the documentation, rather than just using the actual markdown footnote formatting which just makes it less accessible.