refactor!: remove uuid and rand dependencies where applicable

[amrbashir]

ref: #7756

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue [meta] Breaking changes before v2-beta release #7756
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
• I have added a convincing reason for adding this feature, if necessary

Other information

[amrbashir]

There is a couple of places that still use rnd and uuid crates:

1. isolation pattern still uses uuid, not sure if we can replace it with a simple counter, cc @chippers
2. csp nonce and asset protocol range requests -> migrated to the lighter getrandom crate in d398300

[chippers]

There is a couple of places that still use rnd and uuid crates:

1. isolation pattern still uses uuid, not sure if we can replace it with a simple counter, cc @chippers
2. csp nonce and asset protocol range requests -> migrated to the lighter getrandom crate in d398300

it's used so that it's unpredictable and because the output chars are always valid as a schema suffix. using getrandom to generate 128 bits and using lowercase hex as the output should have the same effect here.

i've noticed some code that used uuid is replaced with smaller sizes of things, so take care that it's not problematic there. uuid v4 are often used as trusted random unique numbers because they are 128 bytes (well 122 since some are fixed) that you don't need to check for collisions for in most applications because it's so incredibly unlikely to get another of the same. u32s are much more likely to collide

some places they have been replaced with constants (like the event listener object and function names) which was seen as undesirable before to discourage people from using it manually and going through the proper api instead.

[amrbashir]

it's used so that it's unpredictable and because the output chars are always valid as a schema suffix. using getrandom to generate 128 bits and using lowercase hex as the output should have the same effect here

I will leave that one using uuid for now, at least it is only active when using isolation pattern and the main goal for this PR was to remove it from public API.

i've noticed some code that used uuid is replaced with smaller sizes of things, so take care that it's not problematic there. uuid v4 are often used as trusted random unique numbers because they are 128 bytes (well 122 since some are fixed) that you don't need to check for collisions for in most applications because it's so incredibly unlikely to get another of the same. u32s are much more likely to collide

the u32s are only incrementing so it shouldn't collide with itself, there maybe other ids that could have the same value but they are used in other places.

some places they have been replaced with constants (like the event listener object and function names) which was seen as undesirable before to discourage people from using it manually and going through the proper api instead.

Yeah, I wasn't aware of the history behind that, I could use getrandom in this case but may I ask why it was discouraged? I mean we don't ever provide support for those who uses it directly and we can break it without any notice.

[chippers]

Yeah, I wasn't aware of the history behind that, I could use getrandom in this case but may I ask why it was discouraged? I mean we don't ever provide support for those who uses it directly and we can break it without any notice.

just to avoid the typical "spacebar heating" problem if the behavior does change - and we should explicitly mark somewhere that it is unstable

[amrbashir]

could change the const from

function_name: "_listeners_function_id_",
object_name: "_listeners_object_id_",

to

function_name: "_internal_listeners_function_id_",
object_name: "_internal_listeners_object_id_",