Truncation in specified profile interpolation kernel for profile_size>100

### Are there any linked Issues or Pull Requests?

_No response_

### Brief description
When using the `specified_profiles` initialisation option, `profile_interp_kernel_mod` stores profile values in fixed-size arrays:

- `profile_data(100)`
- `profile_heights(100)`

This imposes a hard limit of 100 profile points and can silently truncate larger profiles.

### Why this matters
While 100 profile points are usually sufficient for standard setups, this limit restricts high-resolution configurations (>100 vertical layers) that require a direct, non-interpolated mapping of the input profile.

### Current behavior
Profiles with more than 100 points are cut off by the fixed-size arrays in:
`science/gungho/source/kernel/initialisation/profile_interp_kernel_mod.F90`.

### Proposed fix / workaround
- Ideally replace fixed-size arrays with dynamically-sized arrays (allocated?), or pass the arrays directly (PSyclone issue [#1312](https://github.com/stfc/PSyclone/issues/1312)), or simply increase the array size to something more reasonable while waiting for [#1312](https://github.com/stfc/PSyclone/issues/1312)).

### Further details of the issue.

_No response_

Start in science/gungho/source/kernel/initialisation/profile_interp_kernel_mod.F90 and inspect how specified_profiles populates profile_data(100) and profile_heights(100). Determine how profiles larger than 100 points are handled, then verify that a profile with more than 100 points is no longer silently truncated without relying on an undefined allocation approach.

Written by the indexing model from the issue text.