Sort imports

It's been bothering me lately the way we structure our imports. I personally like
structuring things like:
- standard lib imports
- github imports
- things we actually take from Pelican

namespace_registry/client_commands.go

@@ -19,8 +19,6 @@
 package nsregistry
 
 import (
-	"github.com/pkg/errors"
-
 	"bufio"
 	"crypto/ecdsa"
 	"encoding/hex"
@@ -32,10 +30,12 @@ import (
 	"github.com/lestrrat-go/jwx/v2/jwa"
 	"github.com/lestrrat-go/jwx/v2/jwk"
 	"github.com/lestrrat-go/jwx/v2/jwt"
+	"github.com/pkg/errors"
+	log "github.com/sirupsen/logrus"
+
 	"github.com/pelicanplatform/pelican/config"
 	"github.com/pelicanplatform/pelican/director"
 	"github.com/pelicanplatform/pelican/utils"
-	log "github.com/sirupsen/logrus"
 )
 
 type clientResponseData struct {

namespace_registry/registry.go

@@ -37,16 +37,16 @@ import (
 	"github.com/gin-gonic/gin"
 	"github.com/lestrrat-go/jwx/v2/jwk"
 	"github.com/lestrrat-go/jwx/v2/jwt"
-	"github.com/pelicanplatform/pelican/config"
-	"github.com/pelicanplatform/pelican/oauth2"
-	"github.com/pelicanplatform/pelican/param"
 	"github.com/pkg/errors"
 	log "github.com/sirupsen/logrus"
-
 	// use this sqlite driver instead of the one from
 	// github.com/mattn/go-sqlite3, because this one
 	// doesn't require compilation with CGO_ENABLED
 	_ "modernc.org/sqlite"
+
+	"github.com/pelicanplatform/pelican/config"
+	"github.com/pelicanplatform/pelican/oauth2"
+	"github.com/pelicanplatform/pelican/param"
 )
 
 var OIDC struct {