feat: Added Project object to Feast Objects

[EXPEbdodla]

What this PR does / why we need it:

1. Based on PR fix: Optimize SQL Registry proto() method #4425 discussion, Added support for Project object for all registry's in feature definitions. Defaults to project in feature_store.yaml if not specified. Syncs projects content in registry (table) from feast_metadata on initialization. Opens up an option to specify multiple projects in single repository (Needs more work).
2. Added a registry configuration purge_feast_metadata to stop using feast_metadata table because list_project_metadata may be used by clients. Instead of deleting that, added a configuration to stop populating table and switch to projects specific methods.
3. Refactored registry methods _prepare_registry_for_changes and _get_registry_proto methods in registry.py. Refactored proto() methods in sql.py and snowflake.py.
4. Corrected RegistryConfig model. new() method in registry.py is blocking RegistryConfig inheritance. Removed it and corrected the tests accordingly. Now we can defined configs specific to registry instead of defining all at RegistryConfig class.

Which issue(s) this PR fixes:

Misc

[tokoko]

Why are both of these necessary? what's the difference. btw, All Feast exceptoins should extend FeastError.

[dmartinol]

@tokoko I noticed the same while doing the latest refactory but I didn't want to extend the scope of changes too much. Looks like other duplications are there like PermissionObjectNotFoundException and DataSourceObjectNotFoundException. Can we remove all of them (in a dedicated ticket maybe)?

[EXPEbdodla]

I'll extend the FeastError for ProjectNotFoundException.
Reasons for having two exceptions: Just followed the current convention.
ProjectNotFoundException --> Exception thrown when the DELETE calls are made and project is not found.
ProjectObjectNotFoundException --> Exception thrown when GET calls are made and project is not found. _get_object method passes two args (name, project) when object is not found. I don't want to add another if else logic to filter out project.

[tokoko]

@dmartinol yeah, this just looks weird. Probably best to defer removal until after this is merged, though.. just to avoid a messy rebase

[dmartinol]

in case, remember an item in the next Release Notes to remind clients to replace any try/except that may have used those duplicate errors.

[tokoko]

FYI @dmartinol

[EXPEbdodla]

Fixed Integration tests. Removed test_remote_online_store.py apply step because Client Store Registry Apply brings back the server and client registry store states to the contents in the repository (Repository missing Permissions. Permissions are applied through store.apply() method). Seems like bug in previous versions which let it work. Did some refactoring to registry so it's showing up as error now.

[EXPEbdodla]

@tokoko Please take a look at this PR when you get a chance.

[tokoko]

looks good, can you also add usage example in quickstart, just an example of creating a project and specifying some tags.

[EXPEbdodla]

looks good, can you also add usage example in quickstart, just an example of creating a project and specifying some tags.

Updated quick start document and feast init functionality to include Project object.

[tokoko]

lgtm, thanks