Some "insecure" options are hardcoded to true

[wkloucek]

Describe the bug

Some REVA "insecure" configurations default to true.

Expected behavior

"insecure" options (most of the time it's SSL cert validation check skip) must be configurable and default to false.

Actual behavior

some "insecure" options default to true, eg.

• reva/cmd/reva/main.go

  Line 114 in a133b60

  rhttp.Insecure(true),

• reva/cmd/reva/download.go

  Line 108 in 8485d40

  rhttp.Insecure(true),

• reva/pkg/cbox/utils/tokenmanagement.go

  Line 67 in a8c6140

  rhttp.Insecure(true),

GRPC connections use also the insecure option (https://grpc.io/docs/guides/auth/#go)

• reva/pkg/rgrpc/todo/pool/pool.go

  Lines 87 to 90 in 63cd968

  	func NewConn(endpoint string) (*grpc.ClientConn, error) {
  	conn, err := grpc.Dial(
  	endpoint,
  	grpc.WithInsecure(),

[wkloucek]

is no longer be the case on "edge" branch