Support more locking kind

[josephsumabat]

Context: Support FOR UPDATE Of tablename and FOR SHARE OF tablename syntax for Postgresql:

This allows a the FOR UPDATE SKIP LOCKED behaviour when you have a LEFT OUTER JOIN with a nullable side. Currently you will get the error:

FOR UPDATE cannot be applied to the nullable side of an outer join

The workaround currently using esqueleto is to do seperate queries and then join them manually if you want to select rows for an update while skipping locked rows (or to just do a raw query). I ran into this situation at work.

See: https://www.postgresql.org/docs/current/sql-select.html namely:

FOR { UPDATE | NO KEY UPDATE | SHARE | KEY SHARE } [ OF table_name [, ...] ] [ NOWAIT | SKIP LOCKED ] [...] ]

also documented in MySQL: https://dev.mysql.com/doc/refman/8.0/en/select.html

    [FOR {UPDATE | SHARE}
        [OF tbl_name [, tbl_name] ...]
        [NOWAIT | SKIP LOCKED]
      | LOCK IN SHARE MODE]
    [into_option]

Usage example would be

select $ do
    (p :& bp) <- from $ 
        table @Person
        `innerJoin` table @BlogPost
            `on` do
                \(p :& b) -> p ^. PersonId ==. b ^. BlogPostAuthorId
                EP.forUpdateOf (p :& b) EP.skipLocked
    return p

• [x] Bumped the version number.
• [x] Documented new APIs with Haddock markup.
• [x] Added @since declarations to the Haddock.
• [x] Ran stylish-haskell and otherwise adhered to the style guide.

After submitting your PR:

• [x] Update the Changelog.md file with a link to your PR.
• [ ] Check that CI passes (or if it fails, for reasons unrelated to your change, like CI timeouts).

[josephsumabat]

@parsonsmatt I've changed the monoid instance to concatenate postgres locking clauses (which results in a valid query) and prioritize general locking clauses over postgres ones.

[josephsumabat]

Past few commits were just updating documentation and version number