[Bug]: Opening Node Profile uuid causing problems

### What happened?

Hi we are using the feature `commands.writeProfile` to write out only a single group node from a session.

use case for us:
- we have a session with a lot of source but only want to reopen one source with annotation
- we only writeProfile for this one sorucegroup and can open the resulting file in a new RV

Issue:

When reading back in that file everything works normally in most cases.
However when the uuid that get's created has a single "e" in it RV can't open the GTO file.

example uuid that cause issues:
328e4978, 1e111111, 4312e934, ...

We expect RV tries to read this in as an exponential notation and that's why it's causing issues.

### List all the operating systems versions where this is happening

any

### On what computer hardware is this happening?

any

### Relevant console log output

```shell
ERROR: parsing GTO file "/path/to/file/node_profile.rv" at line 12, char 8 : syntax error
ERROR: read failed, opening .gto file "/path/to/file/node_profile.rv", failed to parse text GTO (0)
```

### Environment variables

_No response_

### Extra information

_No response_

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Start at the commands.writeProfile entry point and follow how the generated node profile is written and then read by the text GTO parser. Reproduce the failure with UUIDs such as 328e4978 or 1e111111, and compare it with a UUID that does not contain a single “e”; done means the resulting profile opens successfully in RV for all UUID forms.

Written by the indexing model from the issue text.