Handling and display of streams with duplicate names

[corylown]

POD allows users to create multiple streams with the same name. Normally a stream's slug is generated from the name, but to prevent duplicate slugs POD will append a UUID to distinguish between streams with the same name. This behavior is not clear in the UI and may cause confusion. As an example, here are two streams with the name test:

They appear identical in the UI aside from the URL used to address them. In the database you can see that the slug for the second one has a UUID appended. The POD UI should more clearly indicate the unique slug for each stream:

 [#<Stream:0x000055a26d3ca720
  id: 44,
  name: "test",
  organization_id: 5,
  default: false,
  created_at: Mon, 04 Dec 2023 15:32:26.391602000 UTC +00:00,
  updated_at: Mon, 04 Dec 2023 15:32:26.391602000 UTC +00:00,
  slug: "test",
  status: "active">,
 #<Stream:0x000055a26d3ca568
  id: 45,
  name: "test",
  organization_id: 5,
  default: false,
  created_at: Mon, 04 Dec 2023 15:32:36.092311000 UTC +00:00,
  updated_at: Mon, 04 Dec 2023 15:32:36.092311000 UTC +00:00,
  slug: "test-7687cf40-7cc1-48d2-b5ca-5d28fce251b3",
  status: "active">] 

This problem is made more confusing when a stream with a duplicate name is archived and not displayed in the UI. It can make it appear that files uploaded to the archived stream have disappeared (if the user was expecting the files to be uploaded to the un-archived stream with the same name).