add standard build methods for easier discovery

[w3irdrobot]

Description

Add standard builder and build methods for easier crate discovery for new developers.

Notes to the reviewers

Completely unasked for. Just something I happen to run into while writing some documentation and thought it'd be a nice addition. Purely for quality of life. No underlying functionality changes. Actually these just delegate the calls to existing methods. If this is wanted, we could discuss deprecating existing methods for new ones if you want to prevent confusion with multiple methods doing the same thing.

Checklists

All Submissions:

• I followed the contribution guidelines
• I ran make precommit before committing

New Features:

• I've added tests for the new feature
• I've added docs for the new feature

[yukibtc]

I'm not convinced about this change.

Since this is a builder, maybe the building methods can all be renamed with build name/prefix, like:

// Build an event
.build(keys)?;

// Build an unsigned event
.build_unsigned(public_key);

// Build POW event
.build_pow(keys, diffculty)?;

But I'm not convinced of this change either.

IMO the current names (to_event, to_pow_event and to_unsigned_event) are more readable, easy to understand what they do when reading/writing the code.

What do you think? @benthecarman @rustedmoon

[benthecarman]

I always use to_event, I think @yukibtc's function names makes the most sense if more we're added.

[yukibtc]

@w3irdrobot a solution that you can apply locally, if you prefer those names, is to create a trait and implement it for EventBuilder:

pub trait Wrapper {
    fn sign(self, keys: &Keys) -> Result<Event, Error>;

    fn build(self, pubkey: XOnlyPublicKey) -> UnsignedEvent;
}

impl Wrapper for EventBuilder {
    fn sign(self, keys: &Keys) -> Result<Event, Error> {
        self.to_event(keys)
    }

    fn build(self, pubkey: XOnlyPublicKey) -> UnsignedEvent {
        self.to_unsigned_event(pubkey)
    }
}