New version: FiniteGroups v0.3.0

[JuliaRegistrator]

• Registering package: FiniteGroups
• Repository: https://github.com/jayren3996/FiniteGroups.jl
• Created by: @jayren3996
• Version: v0.3.0
• Commit: 96c796495138443d9c8ef1ff6c9964979699eee0
• Reviewed by: @jayren3996
• Reference: jayren3996/FiniteGroups.jl@96c7964#commitcomment-187096882
• Description: Julia package finite group theory calculation.
• Release notes:

First registered 0.3.0 (previous registered version: 0.2.4). A correctness, robustness, and documentation release addressing two rounds of code review. Full test suite green (11696 assertions).

## Breaking changes
- `repname(g, i)` no longer accepts a `convention` keyword (the second naming scheme never existed).
- `permutationgroup(0)`/`permutationgroup(1)` now return the trivial group, and negative `n` is rejected.
- `proj_reps` and `irreps(::PointGroup; R=true)` now drop equivalent duplicates.
- Point-group accessors (`operation`/`matrix`/`rotation`/`irreps`) return copies instead of aliasing package globals.
- `permutation`, `FiniteGroup`, `cover_group`, `oplus`, and `check_group` now validate their input and throw informative errors instead of producing garbage, hanging, or `BoundsError`.

## Fixes
- `proj_to_irrep`/`block_decomposition`: produce real blocks for real reps containing complex irreps, and accept mixed real/complex irrep lists.
- `real_irreps`: select the real form via the Frobenius–Schur indicator rather than storage type.
- Burnside: handle the one-class group and orthonormalize split bases.
- `chiral_proj_reps`: use `Hermitian` (not `Symmetric`) for the chiral operator.
- Dixon: validate the modular class-algebra split and the recovered root-of-unity multiplicities.
- `equivalent_transform`: handle 1D irreps.

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. AutoMerge Guidelines are all met! ✅

Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round (~20 minutes).

2. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.