#43 Add javadoc copyright footer and brand CSS

[krh372]

Summary

• Javadoc previously had no copyright notice and used the plain default styling.
• Added a bottom footer to the root maven-javadoc-plugin config: "Copyright (c) {currentYear} Namazu Studios LLC. All rights reserved." (applies to every module since the plugin is configured once at the root).
• Added src/main/javadoc/stylesheet.css with brand colors (hot pink #FF0099, navy #0D1335) applied via the raw -stylesheetfile javadoc option (Maven's own addStylesheets/stylesheetfile parameters only resolve paths relative to each module's own src/main/javadoc/, which doesn't work for a single shared file across an 84-module reactor).
• Fixed a contrast issue found during review: non-link text in the nav bars (e.g. "Package", "Class" breadcrumb labels) and the active class-summary tab button were dark text on the new navy background. Explicit white text color added for nav bars and the active tab.

Test plan

• Generated javadoc for sdk-model locally (mvn -pl sdk-model javadoc:javadoc) and visually confirmed:
  • Copyright footer appears on every page
  • Brand CSS colors applied (navy nav bars, hot pink links/tabs)
  • Nav bar text and active-tab text are readable (white on navy) after the contrast fix

Closes #43

[ptwohig]

You should give this one a visual pass. I tried to apply it to Crossfire's javadocs and it looked terrible. If the text is hot pink it's a bit much unless we make the whole page navy.

[ptwohig]

It looks like it got wrecked - https://apidocs.namazustudios.com/?product=elements&version=3.9.0-SNAPSHOT-0f25e2102&uri=javadoc%2Findex.html

Need to fiddle with the CSS to get it looking better.

[krh372]

@ptwohig Is there a way to test this with your CSS additions to make sure there are no conflicts?

[ptwohig]

@krh372 Every push you make to any branch will result in the docs being deployed to the site. So you can review it there. Unfortunately, it takes a whole build to do that.