feat(branding): add wordmark and logo layouts

[ReenigneArcher]

Description

Add a standalone LizardByte wordmark and two logo layouts: lettering to the right of the logo and lettering below it.
The lettering is outlined from the supplied reference and uses the existing logo's green gradient, scaled to the
wordmark bounds. Both combined layouts embed the original logo's vector path and gradient.

All three SVGs have transparent backgrounds and require no fonts, linked assets, or embedded raster images.
Add a branding asset index with previews and usage notes.

Screenshot

Wordmark:

Horizontal layout:

Vertical layout:

Issues Fixed or Closed

Roadmap Issues

Testing

• Rendered all three SVGs with Sharp and visually checked dark and white backgrounds and smaller display sizes.
• Parsed the SVGs to verify identical wordmark outlines and gradient definitions across all three layouts,
  valid internal references, accessible titles, transparency, and no external dependencies or clipping in the layouts.
• Compared the embedded logo paths, transforms, and original gradient definitions with logo.svg; they are unchanged.
• git diff --check passed.
• No repository tests were added because this change only adds static branding assets. XML and rendering checks
  validated the assets directly; no application or build behavior changed.

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
• refactor: Code change that neither fixes a bug nor adds a feature
• perf: Code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit
• BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Code has been commented, particularly in hard-to-understand areas
• Code docstring/documentation-blocks for new or existing methods/components have been added or updated
• Tests have been added or updated for new or modified functionality, including regression tests for bug fixes

AI Usage

See our AI usage policy.

• AI tools were used while preparing this PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud