Add ButtonRepresentable/TextRepresentable protocols for rendering Alert/Confirmation Dialog/Menu content

[ky-is]

Followup to #150 and #125

ButtonRepresentable protocol

• Defines a common interface for Views with an action, label, and optional role
• Conformed to by Button, Link, NavigationLink, ShareLink

TextRepresentable protocol

• Allows unwrapping Text from Views with a primary Text attribute
• Conformed to by Label, Text

This simplifies the code a bit and supports more cases for displaying these views in Alert, Confirmation Dialog, and Menu contexts. I've attached a demo view below for testing these changes.

Let me know if this approach looks good!

---

• REQUIRED: I have signed the Contributor Agreement
• REQUIRED: I have tested my change locally with swift test
• OPTIONAL: I have tested my change on an iOS simulator or device
• OPTIONAL: I have tested my change on an Android emulator or device

---

import SwiftUI

struct ContentView: View {
    @State private var buttonSelection: String?
    @State private var navigationString: String?
    @State private var showAlert = false
    @State private var showConfirmationDialog = false

    private let url = URL(string: "https://skip.tools")!

    var body: some View {
        NavigationStack {
            ScrollView {
                Section {
                    VStack {
                        Text("Selected button: \(buttonSelection ?? "nil")")
                        actionButtons(label: "VStack")
                    }
                    .buttonStyle(.bordered)
                }

                Section {
                    VStack {
                        Button("Alert") { showAlert = true }
                            .alert("Alert", isPresented: $showAlert) {
                                actionButtons(label: "Alert")
                            } message: {
                                Label("Alert message in a Label", systemImage: "heart")
                            }
                        Button("Confirmation Dialog") { showConfirmationDialog = true }
                            .confirmationDialog("Confirmation Dialog", isPresented: $showConfirmationDialog) {
                                actionButtons(label: "Alert")
                            } message: {
                                Button("Confirmation message inside a button") {}
                            }
                        Menu("Menu") {
                            actionButtons(label: "Alert")
                        }
                    }
                    .buttonStyle(.borderedProminent)
                }
            }
            .navigationDestination(for: String.self) { navigationString in
                Text("From: \(navigationString)")
            }
        }
    }

    private func actionButtons(label: String) -> some View {
        Group {
            Label("\(label) Label", systemImage: "heart")
            Button("Button") { buttonSelection = label }
            Link("Link", destination: url)
            Link(destination: url) { Label("Link+icon", systemImage: "heart") }
            ShareLink(item: url)
            ShareLink(item: url) { Text("Share") }
            NavigationLink("NavigationLink", value: label)
        }
    }
}

[aabewhite]

Awesome! Will take a look when I get through my current task

[aabewhite]

Couple of comments, but overall looks great

[aabewhite]

It isn't intuitive, but should use ComposeBuilder.from { bridgedLabel }. The "view:" constructor is for when we know the view is something other than another ComposeBuilder

[aabewhite]

You should use the literal constructors or make this a LocalizedStringKey, otherwise there's no way to localize this string