Upgrade virtual project fields from custom_fields to custom_fields2

[hudson-newey]

At the moment, the project model is using the deprecated custom_fields property instead of the new custom_fields2

baw-server/app/models/project.rb

Lines 118 to 133 in 1bca6cb

	custom_fields: lambda { |item, user|
	# do a query for the attributes that may not be in the projection
	# instance or id can be nil
	fresh_project = item.nil? || item.id.nil? ? nil : Project.find(item.id)
	project_hash = {}
	project_hash[:site_ids] = fresh_project.nil? ? nil : fresh_project.sites.pluck(:id).flatten
	project_hash[:region_ids] = fresh_project.nil? ? nil : fresh_project.regions.pluck(:id).flatten
	project_hash[:owner_ids] = fresh_project.nil? ? nil : fresh_project.owners.pluck(:id).flatten
	project_hash[:image_urls] = Api::Image.image_urls(fresh_project.image)
	project_hash.merge!(item.render_markdown_for_api_for(:description))
	# access level for the current user - useful for showing users what their current permission level is
	project_hash[:access_level] = Project.access_level(item, user)
	[item, project_hash]
	},

Because custom_fields doesn't work with projection conditions, project models are not returning the expected result from filter requests that contain projections