[WIP][SPARK-3247][SQL] An API for adding foreign data sources to Spark SQL

**Work in progress - APIs may change**

This PR introduces a new set of APIs to Spark SQL to allow other developers to add support for reading data from new sources.  As an example, [a library is included for reading data encoded using Avro](https://github.com/marmbrus/spark/blob/foreign/sql/core/src/main/scala/org/apache/spark/sql/avro.scala).

New sources must implement the interface `BaseRelation`, which is responsible for describing the schema of the data.  This base relation must also implement at least one `Scan` interface, which is responsible for producing an RDD containing row objects.  The [various Scan interfaces](https://github.com/marmbrus/spark/blob/foreign/sql/core/src/main/scala/org/apache/spark/sql/foreign/package.scala#L50) allow for optimizations such as column pruning and filter push down, when the underlying data source can handle these operations.

External data sources can be accessed using either the programatic API or using pure SQL.  For example, the included Avro library could be called from Scala query DSL as follows:

```scala
import org.apache.spark.sql.avro._

val results = TestSQLContext
  .avroFile("../hive/src/test/resources/data/files/episodes.avro")
  .select('title)
  .collect()
```

The same can be done in pure SQL, for example from the SQL command line or JDBC interface.

```sql
CREATE FOREIGN TEMPORARY TABLE avroTable
USING org.apache.spark.sql.avro
OPTIONS (path "../hive/src/test/resources/data/files/episodes.avro");

SELECT * FROM avroTable;
```

TODO:
 - [ ] Move command refactoring into separate PR
 - [ ] Transition parquet and json support to new API
 - [ ] Figure out how to package data sources and their dependencies
 - [ ] Examples / implementation of more advanced scan types
 - [ ] Support for foreign catalogs
 - [ ] Introspection like `describe` for foreign tables.
 - [ ] More tests
i think it is slightly confusing to make this a package object that extends DataSource for a few reasons

1. it is less common for a package object to implement a lot of stuff
2. based on the fact that you have an implicit class AvroContext, I'm assuming users would usually import avro._. in this case, createRelation is exposed as well